Platform Release 8 August 2018
With the new update action changeDestination, a
ConfigurationError can be fixed (common causes are deleting the destination queue, deleting the access credentials, or removing the permission to push messages into the queue).
We have modified our handling of delivery failures caused by
- A production project has up to 24 hours to fix the configuration
- A development or staging project has up to an hour to fix the configuration
After that, we’ll drop the messages, and will not attempt to deliver further messages. In this case, the subscription gets the status
ConfigurationErrorDeliveryStopped. For more information, see the updated Delivery Guarantees.