Problems with notifications on CMS and builds

What to do

• Check whether your product depends on DatoCMS. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2022-08-04 15:54 UTC and 2022-08-04 15:54 UTC may need a replay.

• Subscribe to DatoCMS's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=datocms works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from DatoCMS 1

1. resolvedAug 4, 2022, 3:54 PM UTC

   Resolved — The incident has been resolved. Monitoring — A fix has been implemented by our partner and they are monitoring the result. Identified — One of our partner (Pusher) is currently having an issue. This could prevent our admin interface to show a notification for actions such as: create a new field, update a field, destroy a field, forking an enviroment, duplicating a site, uploading a new upload and so on. Please, refresh your browser page as the underneath operation might have been completed successfully even if no notification is shown. Follow this issue ( https://status.pusher.com/incidents/k8bxxnb3z35y ) to get the most recent updates. Also, this could lead to some builds failing with this message: Could not subscribe to real-time events! Sorry for the inconvenience

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.