API by Zapier Stop on Error: a Sume 202 is accepted, not finished

If you call Sume from API by Zapier with the new Stop on Error toggle on, a green step only means Sume accepted the submit: an async or webhook submit returns 202 with a job id and polling URLs, and a sync submit returns the same envelope after at most 30 seconds, whether or not the job is terminal. The next step should read terminal and result_ready, not assume the video exists.

Zapier's community post I read on 2026-10-03 says only that API by Zapier gained a Stop on Error toggle; it does not say which statuses count as errors, so confirm that in a test Zap before you rely on it. Sume's behavior is from Jobs and results and Errors and rate limits, also read 2026-10-03. The Zapier post is the source for the toggle.

What does each Sume response mean for the Zap?

Use the first step to learn whether the job exists, and a separate path for the wait. Send Idempotency-Key from a stable value in the trigger, such as the record id, so a replayed Zap returns the original job instead of a second paid one.

What should the toggle not be trusted with?

Do not use Stop on Error as a replacement for a status check. A job can fail after the submit succeeded, and that failure arrives as a failed job or a job.failed webhook, not as an error on the submit step. Read the failure from the job record and branch on it in a later step.