Skip to content

Retry failed workflow when scheduling is stuck#38

Merged
fazpu merged 1 commit into
mainfrom
fix/retry-failed-workflow-scheduling
May 12, 2026
Merged

Retry failed workflow when scheduling is stuck#38
fazpu merged 1 commit into
mainfrom
fix/retry-failed-workflow-scheduling

Conversation

@fazpu

@fazpu fazpu commented May 12, 2026

Copy link
Copy Markdown
Member

Summary

  • keep the normal workflow eligibility pass unchanged
  • add a narrow fallback that retries the latest failed workflow only when no normal workflow is eligible
  • bypass only run_every for that same failed workflow; all other gates still apply
  • add regression coverage for inner success -> outer failure -> outer retry, and for not preempting normal eligibility

Verification

  • uv run ruff format src/loopy_loop/scheduler.py src/tests/test_scheduler.py src/tests/test_must_follow_success.py
  • uv run ruff check src/loopy_loop/scheduler.py src/tests/test_scheduler.py src/tests/test_must_follow_success.py src/tests/test_coordinator_app.py
  • uv run pytest src/tests/test_scheduler.py src/tests/test_must_follow_success.py src/tests/test_coordinator_app.py
  • uv run pytest
  • uv run pyright

Note: one parallel uv formatting invocation hit a transient shared .venv install race; rerunning formatting serially passed.

@fazpu fazpu merged commit 0e5331a into main May 12, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant