52310: Notification TTL has expired

This error occurs when a notification is still being processed or waiting for delivery after its ttl value has expired. In Notify, ttl defines how long a notification remains valid, from 0 to 2419200 seconds. A value of 0 allows only an immediate delivery attempt and does not store the notification for later delivery.

• The request used a ttl value that was too short for the number of recipients or bindings being processed.
• The notification targeted identities or tags that required more processing time, and the service hit normal Notify throughput limits during that window. Notify services have a default limit of 100 notifications per second per service instance, with higher throughput available by request.
• A push recipient device was offline until the ttl elapsed, so Notify could no longer attempt delivery.

• Increase the ttl value so the notification stays valid long enough for processing and delivery. Use a value that matches your expected delivery window and keep it within 0 to 2419200 seconds.
• Avoid using a ttl of 0 unless you want a single immediate attempt with no stored delivery for offline devices.
• Reduce the number of recipients in a single request or spread large sends across multiple requests so your traffic stays within your service's throughput expectations.
• Review your Notify service logs in Console to confirm whether the request was accepted and to review delivery attempts for the affected notification. (help.twilio.com)
• If you are planning new notification workflows, move SMS notifications to Programmable Messaging and use platform-specific push services such as APNs or FCM. Notify was deprecated in October 2022 and reaches end of life for existing customers on January 31, 2027.

• Notification Resource
• Notify Limits
• How to transition off Notify?