Prompt
Upptime broke after a GitHub change
Latest observation
Oct 27, 2026
OpenAI APIWeb search: off
Upptime can break after GitHub API or workflow changes for a few common reasons. If you want, I can help you troubleshoot the exact failure, but here’s a quick checklist of the most likely causes and fixes:
Common causes
-
GitHub Actions permissions changed
- Workflows may now need explicit
permissions:in the YAML. - Common needed scopes:
contents: writeissues: writepull-requests: writechecks: write
- Workflows may now need explicit
-
GitHub Pages deployment method changed
- If Upptime publishes status pages, it may rely on Pages behavior that has changed.
- Ensure the repo is using the expected Pages source and that Actions are allowed to deploy.
-
Token / secret restrictions
GITHUB_TOKENmay not have enough access for some operations.- If Upptime uses a PAT, make sure it still has the right scopes and isn’t expired/revoked.
-
Workflow syntax / deprecated actions
- GitHub sometimes deprecates old action versions.
- Check for pinned actions that are outdated.
-
Branch protection / default branch changes
- Upptime often writes to the default branch or a docs branch.
- If branch rules changed, pushes from Actions may fail.
-
GitHub API rate limits or endpoint changes
- If the project depends on API calls to create issues, comments, or commit status, a GitHub-side change can cause failures.
What to check first
- Go to Actions → failed workflow run
- Open the log and look for:
Resource not accessible by integrationPermission denied403Not found404GitHub Pages build failed
- Compare the workflow YAML against the latest Upptime docs or template.
Typical fix
Add or verify permissions in the workflow, for example:
permissions:
contents: write
issues: write
pull-requests: write
checks: write
If you want, send me:
- the exact error message from the failed GitHub Action,
- your
.github/workflows/*.yml, - and whether you use
GITHUB_TOKENor a PAT,
and I can tell you the precise fix.