Failure signal
A scheduled workflow is disabled or no longer triggered.
GITHUB ACTIONS INTEGRATION
Know when a GitHub Actions workflow stops running
GitHub shows the state of workflows that run. Upnora answers a different question: was this scheduled workflow actually executed when expected?
Job runs↓
Heartbeat sent↓
Upnora receives it✓
GET /h/YOUR_KEY/YOUR_TOKENWHAT CAN FAIL
Why this job can stop silently.
Failure signal
A backup, test or synchronization step fails.
Failure signal
A workflow stops before its final successful step.
BASIC INTEGRATION
Send the heartbeat after successful work.
Use the unique GET URL provided by your Upnora dashboard. The examples are generic: replace them with your monitor URL and keep it in an environment variable or secret.
run: curl --fail "$UPNORA_HEARTBEAT_URL"; env: UPNORA_HEARTBEAT_URL: {{ secrets.UPNORA_HEARTBEAT_URL }}IMPLEMENTATION NOTES
Keep the signal meaningful.
Store the heartbeat URL as a GitHub Actions secret named UPNORA_HEARTBEAT_URL and put a final curl step after the work that must succeed.
See scheduled task monitoring →Common mistake
GitHub logs do not by themselves show that a scheduled workflow ran at its expected time. Upnora adds that external signal and does not replace GitHub.
Wrong: heartbeat → run the job
Better: run the job → heartbeat
MORE HEARTBEAT INTEGRATIONS
Use Upnora with your stack.
FAQ
GitHub Actions heartbeat monitoring, simply explained.
How do I monitor a scheduled workflow?
Add a final curl step that calls the Upnora heartbeat URL after the work succeeds.
Where should I store the URL?
Store it as a GitHub Actions secret.
Does Upnora replace GitHub logs?
No. GitHub remains the source for logs; Upnora detects missing executions.
ADD A SUCCESS SIGNAL