Failures, support, and protected settings

Diagnose failed work, append support history, and respect protected wallet boundaries.

Last updated: 9/10/2026

Diagnose without resubmitting

Unknown transaction outcomes enter reconciliation before an operator considers another action.

01

Filter failed work

On /operations/failures, use admin.failures.filter. Read admin.failures.loading or admin.failures.error, then use admin.investigation.retry only for a recoverable read failure.

02

Update a support case

On /operations/support, use admin.support-cases.filter, follow admin.support.expense or admin.support.payment, enter an append-only note in admin.support.note, choose admin.support.status, and select Append note (admin.support.append).

03

Respect protected settings

/operations/settings explains the platform deployer wallet boundary. Creation or export requires fresh Privy authentication. The platform deployer cannot own or withdraw customer funds.

Admin failed jobs feed with typed failure and reconciliation details
The failure feed gives operators stable identifiers and states without encouraging a blind payment retry.
Admin support cases with append-only note and status controls
Support updates append an auditable note and persist one truthful case status.