Skip to main content

Retries

In the event of failures, Jiter will try to send your events and cron jobs to your desired endpoint at least 3 more times:

The first retry will occur 3 seconds after the scheduledTime for events and nextScheduledDate for cron jobs.

The second retry will occur 5 seconds after the first retry.

The third retry will occur 10 seconds after the second retry.

Example:

If you have an event scheduled for 12:00:00 AM but we receive a 500 status code from your server:

The first retry will occur at 12:00:03 AM

The second retry will occur at 12:00:08 AM

The third retry will occur at 12:00:18 AM

You need to return any status code between 200 - 299 for Jiter to consider the event or cron job successfully delivered.

You can view the event and cron job history by using the GET /events/:id and GET /cronjobs/:id endpoints.