check-restart

Validate orchestrator restart by inspecting logs and confirming job reconciliation.

Updated Sep 22, 2025

Search Tags:#logs #verification #restart #reconciliation #orchestrator #health-check #job-status

Ready to run

npx skills add https://github.com/tinkermonkey/switchyard --skill check-restart

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: check-restart
Source: https://github.com/tinkermonkey/switchyard/tree/main/.claude/skills/check-restart
Command: npx skills add https://github.com/tinkermonkey/switchyard --skill check-restart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps ensure that a restart of the orchestrator completes cleanly by verifying logs, reconciliation, and the status of active jobs.

Core Features & Use Cases

Validate restart integrity by scanning logs for errors and confirming reconciliation completes.
Confirm that all in-flight jobs resume correctly after the restart and that no tasks are left in limbo.
Use cases include post-deploy validation, incident recovery checks, and routine health verifications during maintenance windows.

Quick Start

Run a restart verification to confirm the orchestrator is healthy and all active jobs have resumed.

Frequently Asked Questions about check-restart

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify an orchestrator restarts cleanly without losing active jobs?▼

To verify a clean orchestrator restart, you need to inspect logs for errors, confirm reconciliation completes, and check that all active in-flight jobs resume correctly without being left in limbo.

What is orchestrator reconciliation and when do I need to check it?▼

Orchestrator reconciliation is the process of validating that in-flight tasks and job states persist correctly across a restart. You need to check it during post-deploy validation, incident recovery, or routine health verifications.

How do I check job status and logs to confirm in-flight tasks resumed after a restart?▼

Checking job status after a restart involves scanning orchestrator logs for errors, verifying reconciliation checkpoints, and enforcing that active jobs meet defined success criteria to ensure tasks resumed properly.

Can I use a health-check to validate pipeline recovery during maintenance windows?▼

Yes, you can run a health-check to validate pipeline recovery during maintenance windows by confirming job state persistence, inspecting logs for errors, and ensuring all active jobs have resumed correctly.

Why does my orchestrator leave tasks in limbo after a restart?▼

Tasks are left in limbo after a restart when reconciliation fails or job state persistence does not meet defined success criteria, preventing in-flight tasks from resuming correctly across the pipeline.

Are there limitations to verifying orchestrator restarts using log inspection?▼

Verifying orchestrator restarts via log inspection is limited to confirming the absence of errors and validating reconciliation status; it cannot fix underlying job state persistence failures or missing checkpoints.