Styxis
Company
Knowledge

Shopify cancellation handoff: separate job acceptance from jobResult evidence

Acceptance of an asynchronous cancellation request is not evidence for a completion notice. Define where cancellation-specific results must be checked.

Accepted is different from cancelled

Acceptance of asynchronous work and completion of order cancellation are different events. Approve a completion notice only after checking the cancellation-specific status, errors and affected order. Receiving a generic job ID does not tell the support owner whether processing is ongoing or has failed. Record request acceptance and result verification as separate handoff stages. [1, 2, 3]

A result field tailored to cancellation

Shopify's 2026-10 announcement adds jobResult of type OrderCancelJobResult to orderCancel. Cancellation runs asynchronously, and the new field supplies cancellation status, errors and the affected order. The existing generic job field continues to work. Availability of the new result is therefore not an incident report that existing integrations suddenly broke. [1]

Define the evidence that permits a notice

The support owner should separate acceptance records from cancellation results. Hold completion notices before result verification, and route errors to the owner of the affected order. Confirm that the result concerns the requested order as well. Define actual status enums and success conditions from the applicable API specification; do not invent state names absent from the short announcement for implementation convenience. [1, 3]

A fixture with acceptance but no result

Define an illustrative request that has been accepted but whose cancellation-specific result has not yet been collected. Expected permission to send a completion notice is false. An actual false waits for result verification. A true result would announce an unverified cancellation and must hold the notice. This fixture does not predict whether the job eventually succeeds. It shows how an unknown outcome affects customer communication. [1, 3]

Check for unsupported success in the handoff table

ExpressionValidator in Truthound Core 3.3.2 can use filter_expr to check a prepared table of result verification and notice permission. It cannot turn an acceptance record into result evidence. Nor does Truthound cancel an order or wait for asynchronous execution. Even while preserving compatibility with generic job-based integrations, run a separate result-verification procedure and do not add completion claims to logs that lack a source result. [1, 2, 3]

Application conditions

Collect cancellation-specific results in 2026-10 or later. Establish actual status enums and completion conditions from the applicable API specification. Do not infer completion from a generic job ID.

Alternatives

Preserve compatibility for integrations using the existing job field while running a separate result-verification procedure. Update support-notice conditions when adopting jobResult.

Limitations

  • Truthound neither cancels orders nor waits for asynchronous work. This article does not invent status enums or error-retry semantics absent from the announcement.

Evidence

Event checked
Subject checked
Modified