Detected task raised/updated/resolved from a sync-plane finding

RECEIVEsync.task.raised

Message

sourcestringrequired

Allowed:readinessconsistencyvalidationmonitoringcatalog_import

source_refstringrequired

issue_idstring

Id of the specific issue on source_ref's product that raised this task (readiness only). Disambiguates multiple blocking issues on the same product so each gets its own task instead of colliding on (source, store, source_ref).

ownertask_ownerrequired

Allowed:merchantsarvexexternal

titlestringrequired

blocks_checkoutboolean

resolvedboolean

When true, this signals the (source, source_ref, issue_id) task should be closed rather than raised — the underlying condition no longer applies.

Headers

message_idstringrequired

Unique per message; consumers de-duplicate on this.

ordering_keystringrequired

The store_id. Guarantees per-store ordering; the catalog/serving tenant boundary (a store belongs to one merchant — see architecture §2a).

occurred_atstring<date-time>required

sequenceinteger<int64>

Monotonic per-connector sequence carried from the origin signal (ingest events only).

trace_idstring

Correlates a chain of events from one originating cause.

schema_versionstringrequired

Try it

Server

ServerCustom server URLOverrides the selected server; the channel address is appended.

Payload

Message payload

Live sending isn't possible for pubsub from a browser tab — copy the sample above and run it against your broker.

Message

{
  "source": "readiness",
  "source_ref": "string",
  "issue_id": "string",
  "owner": "merchant",
  "title": "string",
  "blocks_checkout": true,
  "resolved": true
}