Browse all articles tagged with #retries.
A delayed event reminder arrives after the session ended. The transport recovered, but the message no longer served its purpose.
The main campaign is paused, yet a few messages keep leaving the system. Look for retry workers and jobs already claimed before assuming the pause button is ignored.
A group of destinations starts returning temporary failures. Restarting the campaign from the beginning can increase load and resend messages that were already accepted.
The application reports a timeout and offers Retry. The receiving server may already have accepted the message, even though the application never received the final confirmation.