Failure signal
A Promise rejects during a background task.
NODE.JS INTEGRATION
Monitor Node.js background and scheduled jobs
Asynchronous Node.js jobs can fail through rejected promises, timeouts or a scheduler that stops triggering. Send a heartbeat only after the awaited work has completed successfully.
Job runs↓
Heartbeat sent↓
Upnora receives it✓
GET /h/YOUR_KEY/YOUR_TOKENWHAT CAN FAIL
Why this job can stop silently.
Failure signal
A scheduled Node.js process stops starting.
Failure signal
A worker exits before its asynchronous work finishes.
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.
await runJob(); await fetch(process.env.UPNORA_HEARTBEAT_URL);IMPLEMENTATION NOTES
Keep the signal meaningful.
Use an environment variable for the URL and await the job before calling fetch(). If the job rejects, the heartbeat call is skipped.
See scheduled task monitoring →Common mistake
A Promise that is still running is not proof that the task completed successfully.
Wrong: heartbeat → run the job
Better: run the job → heartbeat
MORE HEARTBEAT INTEGRATIONS
Use Upnora with your stack.
FAQ
Node.js heartbeat monitoring, simply explained.
How do I monitor a Node.js job?
Await the job, then call the Upnora heartbeat URL with fetch().
Where should the heartbeat URL live?
Store it in the environment used by the worker or scheduler.
Can Upnora detect a rejected Promise?
Yes, when the rejection prevents the heartbeat from being sent.
ADD A SUCCESS SIGNAL