published
not discovered

Limits

These are the figures you would otherwise find out during an incident. They are the same on every plan except where a row says otherwise, and we will tell you a month before any of them changes.

the schedule

Attempts, including the first run9
First wait250 ms
Longest wait, and the cap30 s
Time from enqueue to the dead letter, worst case1 min 31.75 s
Clock skew allowed on a scheduled job±2 s

the job

Payload64 KB
Payload, Nightshift1 MB
Runtime before an attempt is abandoned15 min
Idempotency key128 bytes
Enqueue rate, per queue400 a second
Queues, Yard3

arrival

The arrival alert is the thing that fires when nothing fails. Bidewell measures the interval between jobs on a queue over its last two hundred arrivals, and raises the queue when four times the median interval passes with none. It needs forty arrivals before it will say anything, so a queue that has just been created is quiet for a while and says so in the dashboard rather than pretending it is watching.

Arrivals before the alert is armed40
Window the median is taken over200 arrivals
Multiple of the median that raises it4×
Shortest interval it will watch30 s
Longest31 days
A loading bay at night seen from inside, the roller shutter half down and a trailer's rear doors standing in the wet apron beyond it.
attempt 7 · ×128 light

retention

Attempt history, Yard7 days
Attempt history, Works30 days
Attempt history, Nightshift90 days
Dead letter, all planskept until you act
Payloads after a job is deletedpurged within 24 h

The dead letter is the one thing with no expiry. Everything else is a window and the window is on your plan. Pricing