Destination delivery and troubleshooting
Destination delivery and troubleshooting
Open Settings → Integrations → Destinations to check a destination’s last
run, health and errors. Open a decision’s Delivered to block to see where
that particular line went and the reference returned.
Choose which decisions go
Each destination receives only the lines its filter admits; the card shows the
filter as one sentence.
- Which decisions: orders, price changes and stock transfers, in any mix.
Product updates must be selected explicitly; you can then narrow
Product update reasons. The ordinary default excludes product updates. - Buyer scopes and suppliers, from the workspace’s own lists.
- Raised projects only: wait until the project is raised. On by default when
a destination receives orders and nothing else. - Under More: Only the last (days) and Leave out SKUs starting with
(comma-separated prefixes).
A line that stops matching every destination’s filter is withdrawn on the
ledger. Nothing is removed from the destination.
A product update recorded locally only is not eligible for external delivery,
even if you later select Product updates or run a nightly catch-up.
Choose when to send
Tick any of three, under Name and filter:
- As each decision is made: a line lands the moment a buyer commits it.
Pick it for a sheet your team works from during the day. - When a project is raised: the whole project lands at once, after
sign-off. Pick it for a system that places orders. An orders-only destination
with raised projects only first sees its lines here. - Nightly catch-up at 05:00 (workspace time): anything changed or missed
is sent again, and the columns your team filled in are read back. Leave it
on: it is what fills in Reference and Raised at. A destination linked
today has its first catch-up tomorrow.
Link and deliver links the destination at once and sends the first
delivery in the background; the dialog follows it and links straight to the
sheet. Deliver now runs the whole filter at once. The On / Off switch
keeps everything and delivers nothing while off.
Understand the ledger
- Recorded: committed in Twelfth; nothing has left yet.
- Staged: delivered to at least one destination, not yet seen in your
system of record. - Executed: seen in the system of record: a Raised at date on the sheet,
or a raised date reported by your system. A reference alone is acknowledged,
one step short. - Withdrawn: the line no longer matches any destination’s filter.
The decision’s page carries a Delivered to block naming each destination,
the status there, a link to the row where one exists, the reference that came
back, and any error. The exported CSV carries a State column.
Delivered is not the same as executed. A row in an upload workbook is staged
for your team to import. A reference says the receiving system acknowledged
the line; confirmation of execution is a separate result. Exact upload tabs
have no read-back columns, so clearing a row after import does not report
execution to Twelfth. Native Rex writeback confirms its supported changes
against the product in Rex.
Recover a failure
The usual destination policy allows up to five total delivery attempts with
increasing delays. After the limit, the delivery is marked dead; the card offers
Retry all and Recent deliveries offers a per-row Retry. Native Rex
writeback has its own confirmation and unknown-outcome rules; follow its guide
before creating another approval.
A refused credential stops automatic retries until an admin restores the
connection. Edit the credential or share, then use Deliver now or the next
configured trigger. For an API or webhook whose reply was lost, confirm the
receiver honours Idempotency-Key before retrying a potentially real action.
| Health | What to do |
|---|---|
| Healthy | The last delivery landed. Check the decision result if you need execution confirmation. |
| Degraded | Some lines failed. Read their errors under Recent deliveries. |
| Failing | Repeated runs failed. Fix the connection, mapping or receiver before retrying. |
| Connection lost | Restore the spreadsheet share or replace the refused credential. |
| Off | The destination is paused. Its configuration and past results remain. |
Spreadsheet problems
- Viewer share: change it to Editor and recheck.
- File belongs to another workspace: share a separate copy; unlinking does
not move its ownership. - Missing supplier code: correct the inbound supplier mapping before
delivering to supplier-code template tabs. - Row changed by your team: review it in the workbook. Exact upload mode
will not overwrite a row that no longer matches what Twelfth wrote. - Row cleared after upload: exact upload mode leaves it cleared, rather than
filling it again on a later catch-up.
Remove unlinks the destination without deleting records or files on your
side. Turning On / Off off pauses delivery without removing the connection.
Who is notified
- Workspace owners and admins (and any extra address on the destination)
hear when a destination goes failing or loses its connection, when a
delivery gives up, and when a nightly read-back finds a deleted row. The message goes by
email, and to the workspace’s chat channel where one is connected. At most
one message per destination per day. The daily brief carries one line. - The buyer who decided sees a line that gave up, or was executed, on the
ledger entry and on the project’s Raised stage. No email.
Nobody hears about an individual attempt, a retry, or a run that succeeded.