openclaw - 💡(How to fix) Fix Scheduled Live And E2E Checks workflow consistently fails with startup_failure [1 comments, 2 participants]

Summary

The OpenClaw Scheduled Live And E2E Checks workflow has been failing with startup_failure every day since at least 2026-05-01 (runs #1 through #5 and counting).

Evidence

(All runs between 05-04 and 05-10 exhibit the same pattern.)

All runs show 0 jobs created — the workflow fails before any job is scheduled.

Key Observations

1. All scheduled (cron) runs fail with startup_failure — every single daily run since at least May 1st.
2. Manual workflow_dispatch runs succeed — the same reusable workflow was successfully triggered manually on 2026-05-10T12:59:48Z (run ID 25629373900).
3. Other scheduled workflows work normally — CodeQL, Install Smoke, and Control UI Locale Refresh all run successfully on their schedules.
4. The reusable workflow is correctly configured — openclaw-live-and-e2e-checks-reusable.yml has both workflow_dispatch and workflow_call triggers defined, and all secrets are declared in both the caller and the reusable workflow.

Possible Causes

• Missing or expired repository secrets — The caller workflow passes 30+ API key secrets. If any required secret is missing, GitHub Actions may fail to resolve ${{ secrets.XXX }} during the schedule trigger.
• GitHub Actions runner/queue limitations — The large number of secrets and the reusable workflow chain may hit a scheduling constraint for schedule-triggered events.
• Reusable workflow version mismatch — The caller references ./.github/workflows/openclaw-live-and-e2e-checks-reusable.yml, which should always resolve to the latest commit on main, but there may be a caching or resolution issue specific to scheduled runs.

Request

Could a maintainer with repository admin access check:

1. Whether all required secrets listed in .github/workflows/openclaw-scheduled-live-checks.yml are still configured in the repository settings
2. Whether there are any GitHub Actions runner or concurrency limitations affecting this workflow
3. Whether the reusable workflow reference needs to be updated or the workflow file has a syntax issue not caught by YAML validation

Thanks!