Track session continuation

One branch can wait for review while another finishes. Use the continuation filters to find the work you need, then inspect that branch’s recorded events. An email or callback attempt is not proof that the application continued.

Filter the session list

The continuation cards are clickable and apply the matching filter to the current session list:

• Waiting for review shows paused work that still needs a human decision.
• Decision recorded shows work where review is complete but delivery or application processing may still be running.
• Callback needs attention shows work with a stopped or operator-held delivery.
• Waiting for application shows work where the application received the decision but has not acknowledged execution.

Choose the active card again to remove that filter.

Read a mixed session

A session can have several branches. A Mixed state label means at least one branch has progressed while another remains paused or needs attention. Open the session and read each branch rather than treating the session as one state.

Distinguish the recorded events

Repair a stopped delivery

An authorized administrator can open the callback repair panel from the affected branch. Check the incident and delivery identified there before acting. After repair or replay, refresh the history and check the new records. Do not assume a successful replay means the application completed its work.

For application-worker guidance, see Recover a long-paused continuation. It covers credential refresh, branch isolation, checkpoint loss, and restart recovery without treating a receipt as proof of execution.

Advanced multi-stage approvals and third-party continuation connectors are not available in this release.