Failures and Recovery

Planning, approval and application can fail at different stages. Preserve the visible result so you can distinguish them.

Before any Discord write

Fix the reported permission, stale revision or invalid plan condition. Re-analyze/review when context changed. Do not reuse an old approval for a revised draft.

After partial application

1. Read every step outcome.
2. Check actual channels, roles and effective access in Discord.
3. Compare them with the plan’s intended operations.
4. Preserve safe result identifiers and the time.
5. Prepare a bounded correction only after the state is understood.

There is no general automatic rollback of completed Discord changes. Repeating the full request can create duplicates or apply a second mutation.

Uncertain outcome

An interrupted connection or missing confirmation may leave the external outcome unknown. Do not assume failure or success. Inspect state and ask the operator to review retained receipts if necessary. Provide redacted context through Support, never credentials or session cookies.