cleanup-stale-executions

To clean up stale executions, you can run an automated maintenance process that marks long-running or inactive executions as failed and removes old completed entries from the `skill_execution.json` file. This prevents the log from growing too large and identifies hung processes.

A skill execution is marked as failed when it exceeds a specified time limit or has been inactive for too long. This stale execution management identifies running processes that have unexpectedly hung and updates their status to failed in the execution log.

You need to remove old completed executions to ensure the execution log remains manageable and accurate. Regularly clearing successful or failed entries from the `skill_execution.json` file prevents unbounded log growth and maintains system visibility.

Yes, you can automate log management by regularly running a cleanup process that identifies inactive executions. This automated maintenance evaluates process age and status within the `skill_execution.json` file to clear stale records without manual intervention.

No, cleaning up stale executions requires no external dependencies or components. The process operates directly on the `skill_execution.json` file to process entries based on their age and status, functioning independently within your software engineering environment.