Delivery statuses and workflow terms

Use the exact status from an event trace or workflow record to choose the next step. Ingestion receipt, Meta acceptance, and verified Actions execution describe different outcomes.

Provider connection health

get_account_state returns connection.health using the same workspace-specific status as Connections. The existing connection.status is the raw stored connection state; do not substitute it for health.

Value	Meaning	Next step
`not_connected`	No usable bound connection is configured for this workspace, or the stored connection is inactive.	Open Connections and check the selected platform account.
`revoked`	The connection is marked revoked or provider-token revocation completed.	Reconnect the intended platform account if access should resume.
`attention_needed`	Reconnection is required, credentials are missing, the latest stored read failed, or revocation is unfinished.	Inspect Connections and its last-read state; resolve the reported issue before relying on platform data.
`connected`	The active connection has stored credentials and a bound account, without a failed latest read or pending revocation.	Check data freshness and destination delivery separately.

These values describe stored connection evidence. connected can occur before any successful platform read; it does not certify credentials with a new provider request. For Meta, use connection setup and permissions and delivery checks. Provider health is also separate from the Signals diagnostic below.

Signal health

These labels come from the account-scoped get_signal_health diagnostic. The Signals overview presents collection status and arrival metrics separately.

API value	UI label	Meaning
`setup_required`	Setup required	Signal collection or hostname activation is incomplete.
`awaiting_data`	Awaiting data	Setup is active, but no retained arrival evidence exists.
`quiet`	Quiet	Retained arrival evidence exists, but none falls in the selected window or today.
`active_unmeasured`	Measurement pending	Events exist, but required delivery, EMQ, or reconciliation measurements are incomplete.
`needs_attention`	Needs attention	At least one warning or critical diagnostic is active.
`healthy`	Healthy	Event activity and all required measurement categories are recent and have no active warning.

Signal infrastructure

Workspace Signals state

Value	Meaning
`pending`	Setup has started but is not fully active.
`active`	The workspace can receive Signals events.
`inactive`	Signals is not active for the workspace.

Collection hostname

removed_at_cloudflare means Cloudflare removed the managed hostname. Automatic refresh stops; use Re-provision hostname to recover. The removed record remains as history.

Value	Meaning
`pending_validation`	Plainrouter is waiting for DNS or certificate validation.
`active`	The hostname and HTTPS certificate are active.
`failed`	Hostname provisioning or validation failed.
`deactivated`	The hostname is no longer active.
`removed_at_cloudflare`	The managed hostname was removed at Cloudflare and requires re-provisioning.

Destination delivery

Value	Category	Meaning
`queued`	Pending	Waiting for destination delivery.
`sent`	Pending	Sent and awaiting the destination result.
`retrying`	Pending	Retrying a transient failure.
`accepted`	Accepted	Meta accepted the event.
`failed:auth`	Failed	Meta rejected the access token.
`failed:permanent`	Failed	A non-retryable payload or destination error occurred.
`failed:unknown`	Failed	Delivery stopped after an unclassified failure.
`expired`	Terminal	The event exceeded delivery freshness or its retained payload is unavailable.
`skipped:consent`	Terminal	Advertising user-data consent was denied.
`skipped:no_destination`	Terminal	No active destination was configured.
`skipped:duplicate`	Terminal	The destination had already received the event.

What should I do after a delivery fails?

State	Recovery
`failed:auth`	Reconnect Meta, then replay the eligible delivery.
`failed:permanent` or `failed:unknown`	Read the trace explanation. Correct the cause before considering replay; replay preserves the existing payload.
`expired`	Check payload availability and original event time. Replay limits still apply; do not reset timestamps.
`skipped:consent`	Fix consent handling for future eligible events. Skipped deliveries cannot be replayed.
`skipped:no_destination`	Connect the intended destination for future events. This does not replay skipped history.
`skipped:duplicate`	Inspect the original delivery; do not send another purchase with a new ID.

The dashboard’s acceptance-rate denominator includes recent non-test deliveries in the delivery ledger. Its pending count groups queued, sent, and retrying. Its failed count groups the three failed:* states.

Performance measurability

Status	Reason	Meaning
`measurable`	`null`	At least one report exists in the requested window and the latest report is recent.
`not_measurable`	`no_history`	No usable reconciliation report exists for the requested window.
`not_measurable`	`stale_history`	The latest reconciliation report is more than 48 hours old.

Policy decisions

Value	Meaning
`require_approval`	A person must decide in the approval queue.
`block`	At least one safeguard prevents the proposal from proceeding.
`allow`	Policy permits the current phase to proceed. Executable work must receive `allow` again during the execution-time recheck.

Action batch statuses

Value	Meaning
`pending`	Waiting for human approval.
`approved_without_execution`	Human-approved suggest-only recommendation. Terminal and not executed.
`rejected`	Human-rejected recommendation. Terminal.
`blocked`	Stopped by policy or a safety condition. Terminal.
`halted`	The Meta execution kill switch stopped the batch. Earlier verified changes can remain; inspect each action and receipt. Terminal and cannot be approved again.
`approved`	Human-approved for an execution-enabled path and queued for a fresh policy check.
`auto_approved`	Automatically approved by an execution-enabled policy mode.
`executing`	An execution-enabled batch is in progress.
`executed_pending_verification`	A provider write has a durable receipt, but exact verification is still pending. Not Landed.
`compensating`	Plainrouter is restoring provider state and verifying the restoration.
`measuring`	A closed provider-measurement run is active. Explicitly Not Landed.
`completed`	All actions have exact verified provider receipts. Counted as Landed unless marked measurement-only.
`failed`	Execution failed.
`rolled_back`	Prior provider state was restored; inspect the recorded compensation and verification evidence.
`rollback_incomplete`	At least one attempted restoration failed and needs attention.

Action statuses

Value	Meaning
`pending`	The action belongs to a batch awaiting a decision.
`approved_without_execution`	Suggest-only approval. Terminal and not executed.
`rejected`	A person rejected the action. Terminal.
`executing`	Provider execution is in progress.
`executed_pending_verification`	The action has a committed receipt but is not yet exactly verified.
`verified`	The receipt-addressed provider state matches the approved action.
`compensating`	Verified restoration is in progress.
`measuring`	The action belongs to a closed provider-measurement run and is Not Landed.
`execution_uncertain`	Provider commit state could not be resolved safely.
`failed`	Execution or verification failed.
`rolled_back`	The provider change was restored and the restoration was verified.
`blocked`	Policy or an execution boundary stopped the action before execution.

A receipt marked irreversible does not establish restoration. A batch with rollback_incomplete needs investigation even if other actions were restored. Read the exact action and receipt outcomes before retrying or claiming that a provider change was undone.

Can a failed batch later show restoration?

Yes. Current receipt evidence can show late restoration while the historical action or batch status stays unchanged. Inspect disposition and the batch’s restoration_summary through the Actions reads, or expand All details in Inbox. A compensated receipt is evidence of recovery, not a successful original execution.

Core terms

Gateway-verified

A conversion counted as accepted through Plainrouter’s stored delivery and reconciliation records. It does not mean independently audited business revenue.

Meta-reported

A conversion count captured in a stored reconciliation report from Meta for the connected dataset and report date.

Observed gap

Gateway-verified count minus Meta-reported count. It is a count difference, not CPA or incrementality.

Evidence provenance

The source tool, scope, exact fields, observation time, window, and measurability recorded with an Actions proposal.

Human-supplied target

A platform entity selected by a person. It establishes selection only and does not prove current target state.

Ask and Full

Ask is the default: a person approves every change first. In Full mode, the workspace lets changes run automatically without a per-change approval. Every change gets a receipt, and the kill switch stops all changes. Both modes require current admission and provider verification checks.

Suggest only (historical)

An older batch snapshot whose approval terminates without execution. It is no longer a selectable workspace policy mode.

Landed

A production action batch in which every action has a durable provider receipt and an exact matching verification read. Approval or a provider write alone is not Landed.The Inbox display group Done contains verified actions. Historical approved_without_execution recommendations appear separately under Approved, not sent. Check action and batch status together with their receipts before claiming complete provider execution. See Inbox groups.

Executed pending verification

A committed provider action that has not yet reached exact verification. Plainrouter may continue scheduled receipt-addressed reads, but the action remains Not Landed.

Compensation

A safety restoration against the exact receipt target. Plainrouter considers it successful only after a provider read verifies deletion, archive, or the required restored state.

v1 non-recomputable

A historical audit segment whose predecessor links are preserved but whose hashes cannot be fully recomputed from durable row fields.

v2 recomputable

The durable canonical audit segment whose stored rows can be cryptographically recomputed within the current database snapshot.

Get started

Signals

Actions

Reference

Legacy Launcher

Delivery statuses and workflow terms

Provider connection health

Signal health

Signal infrastructure

Workspace Signals state

Collection hostname

Destination delivery

What should I do after a delivery fails?

Performance measurability

Policy decisions

Action batch statuses

Action statuses

Can a failed batch later show restoration?

Core terms

​Provider connection health

​Signal health

​Signal infrastructure

​Workspace Signals state

​Collection hostname

​Destination delivery

​What should I do after a delivery fails?

​Performance measurability

​Policy decisions

​Action batch statuses

​Action statuses

​Can a failed batch later show restoration?

​Core terms

Provider connection health

Signal health

Signal infrastructure

Workspace Signals state

Collection hostname

Destination delivery

What should I do after a delivery fails?

Performance measurability

Policy decisions

Action batch statuses

Action statuses

Can a failed batch later show restoration?

Core terms