Notice history

Operational

ResolvedNovember 01, 2022 at 11:39 AMUTC
The issue is now resolved.
InvestigatingNovember 01, 2022 at 10:47 AMUTC
We are aware of an issue that is preventing users from creating Templates. Our engineering team is currently investigating it. Please wait for new updates, which will be shared here as soon as they are available.

Details: When creating a Template message, you might get the error: `Invalid payload ({"error":{"message":"Error validating access token: The user has not authorized application x.","type":"OAuthException","code":190,"errorsubcode":458,"fbtraceid":"y"}}) `

ResolvedOctober 25, 2022 at 10:40 AMUTC
Meta have marked the issues as resolved on their side. Messaging now appears to be stable and fully functional again.
MonitoringOctober 25, 2022 at 8:55 AMUTC
It seems that the problem has been resolved.

We're still monitoring this issue to make sure that all services have been restored.
IdentifiedOctober 25, 2022 at 8:40 AMUTC
We are aware of a total outage affecting the global WhatsApp network. Meta have acknowledged this issue and are currently investigating.

We will update you as soon as we have further information.

ResolvedOctober 24, 2022 at 7:55 AMUTC
The issue has been identified and fixed.

Please accept our apologies for any inconvenience that this may have caused.
InvestigatingOctober 24, 2022 at 3:23 AMUTC
We are aware of an issue that is preventing users from creating Templates. Our engineering team is currently investigating it. Please wait for new updates, which will be shared here as soon as they are available.

Details: When creating a Template message, you might get the error: `Invalid payload ({"error":{"message":"Error validating access token: The user has not authorized application x.","type":"OAuthException","code":190,"errorsubcode":458,"fbtraceid":"y"}}) `

ResolvedOctober 21, 2022 at 6:20 AMUTC
The issue has been identified and fixed.

Please accept our apologies for any inconvenience that this may have caused.
UpdateOctober 21, 2022 at 1:56 AMUTC
The team has deployed a solution to the issue we are currently monitoring it in order to keep track of it and make sure it is fully resolved.
MonitoringOctober 20, 2022 at 9:32 PMUTC
We are currently investigating this incident that affects the creation and management of templates in the HUB

ResolvedOctober 19, 2022 at 6:40 AMUTC
The issue has been identified and fixed.

Please accept our apologies for any inconvenience that this may have caused.
InvestigatingOctober 19, 2022 at 5:20 AMUTC
We are aware of an issue that is preventing users from creating Templates. Our engineering team is currently investigating it. Please wait for new updates, which will be shared here as soon as they are available.

Details: When creating a Template message, you might get the error: Invalid payload ({"error":{"message":"Error validating access token: The user has not authorized application x.","type":"OAuthException","code":190,"errorsubcode":458,"fbtraceid":"y"}})

ResolvedOctober 14, 2022 at 12:47 PMUTC
The issue has been identified and fixed.

Please accept our apologies for any inconvenience that this may have caused.
InvestigatingOctober 14, 2022 at 8:34 AMUTC
We are aware of an issue that is preventing users from creating Templates. Our engineering team is currently investigating it. Please wait for new updates, which will be shared here as soon as they are available.

Details: When creating a Template message, you might get the error: `Invalid payload ({"error":{"message":"Error validating access token: The session has been invalidated because the user changed their password or Facebook has changed the session for security reasons.","type":"OAuthException","code":190,"errorsubcode":460,"fbtraceid":"x"}}) `

ResolvedSeptember 27, 2022 at 10:51 AMUTC
The issue has been identified and fixed.

Please accept our apologies for any inconvenience that this may have caused.
InvestigatingSeptember 27, 2022 at 7:49 AMUTC
We are receiving reports that some users are unable to add more numbers for Classic Sign-up. Our engineering teams are investigating this issue now. Please wait for new updates, which will be shared here as soon as they are available. We do not have an ETA for resolution at the moment.

ResolvedSeptember 27, 2022 at 10:41 AMUTC
We just resolved the issue!
IdentifiedSeptember 27, 2022 at 10:41 AMUTC
Issue is resolved
InvestigatingSeptember 26, 2022 at 6:58 AMUTC
We are currently investigating this incident.

ResolvedSeptember 20, 2022 at 2:15 PMUTC
Hub access was restored and now appears stable.

This incident has been resolved and will now be closed.
MonitoringSeptember 20, 2022 at 1:01 PMUTC
Access to our 360 client and partner hubs has now been restored.

A recent minor deployment was found to be responsible for causing the outage and has since been rolled-back.

Please accept our apologies for any inconvenience that this outage may have caused. We are continuing to monitor the situation for the time being.
InvestigatingSeptember 20, 2022 at 12:19 PMUTC
It has come to our attention that our 360 client and partner hubs are currently unreachable.

We are currently investigating this incident with high priority.

ResolvedSeptember 23, 2022 at 11:48 AMUTC
This incident has been resolved and will now be closed.
IdentifiedSeptember 20, 2022 at 8:06 AMUTC
The issue has been identified.

The technical team is currently working on the fix.
InvestigatingSeptember 19, 2022 at 7:44 AMUTC
We are receiving reports that some users are unable to add more numbers. Our engineering teams are investigating this issue now. Please wait for new updates, which will be shared here as soon as they are available. We do not have an ETA for resolution at the moment.

Sep 2022 to Nov 2022

360Dialog - Notice history