Implementation Logic
Possible Interruptions
Network issues causing repeated LLM API call failures.
Parsing errors during action execution.
Manual interruptions (e.g., Ctrl-C).
Serialized Storage Structure
All serialized data is stored in an integrated JSON file to minimize future changes to the storage structure. Example:
Recovery Scenarios
Role A fails to select an action:
Upon re-execution, Role A observes the unprocessed message and retries the action.
Role B resumes processing based on the updated message and continues.
Role B fails during action execution:
Upon recovery, Role B resumes directly from the failed action.
Key Recovery Steps
Re-execute from the Message before the interruption:
Messages act as communication bridges between roles. To resume execution, interrupted messages must be reloaded and processed.
Re-execute from the Action before the interruption:
Actions are granular execution units. Recovery ensures actions resume at the exact point of failure.
Result: Breakpoint Recovery Workflow
Command to enable recovery:
Serialized data is stored in ./workspace/storage/team
by default.
Example Execution Flow:
A test case simulates an interruption and recovery:
Recovery Logs:
Last updated