Make 'Process data in order' with Sume job events: what stays ordered

Turn on 'Process data in order' in Make and each Sume callback waits for the previous execution to finish, but that only orders what Make received, not what Sume sent. Sume's docs promise terminal events only and say nothing about delivery order, so key your logic on job_id and the job's own status, never on arrival sequence.

The checks below are drawn from Make's help page and Sume's webhook docs.

What Make documents

What Sume sends

Where ordering can still slip

Sequential execution in Make does not reorder deliveries in time. If job A's first delivery fails and succeeds on a retry 30 seconds later, job B's event may reach Make first. Redeliver can also send a job's event again long after later jobs finished. Each job has one terminal event, plus any redeliveries you request, so the practical fix is not to rely on order at all.

A safe scenario layout

• First module: a data store lookup on job_id. If it exists, stop; otherwise write it.
• Fetch the result from GET /v1/jobs/{id}/result rather than trusting the payload alone.
• Use 'Process data in order' only when your downstream step needs one-at-a-time access, for example a shared spreadsheet. Expect the Make queue to fill faster, and size it with the 667 per 10,000 credits rule.
• If you need a business order, sort by your own field (a row number you sent in the request), not by arrival.