Scheduling messages from your application

Scheduling is handled by your application

WasenderApi does not include a built-in message scheduler. Store the intended send time in your application, then call the send-message API when the message is due.

You can use a job queue, a scheduled worker or a workflow delay. Store a timezone-aware send time so daylight-saving changes and user timezones do not move messages unexpectedly.

A reliable scheduling flow

1. Store the recipient, message, session and intended send time with a unique job ID.
2. When the job is due, confirm it has not been cancelled or sent already.
3. Check the session connection and send within your account’s rate limits.
4. Save the returned message ID and track delivery separately.
5. Handle retryable errors with backoff. For HTTP 429, respect retry_after.

If a request times out after submission, it may already have been accepted. Investigate before resending so a retry does not send the same message twice.

Before you launch

Test with a small queue and an active recipient. A scheduled time is the time your application attempts to send, not a guarantee of delivery at that moment. See sent versus delivered.