Background job infrastructure
Background jobs,
without the infrastructure.
Enqueue work from your app. JobOrc runs it on workers, retries failures, and shows you every attempt.
send-welcome-email
job_88a910·notifications
queued
running
succeeded
01
You write the job. JobOrc executes it.
enqueue
Your Application
execute
JobOrc
work
Background Work
02 · Reliability
Reliable
Retries and recovery are built in. Jobs keep running.
send-welcome-email
attempt 2 of 3 · notifications
- ⟳runningWorker accepted execution14:29:02.104
- ✕failedConnection reset by peer+96ms
- ⟲retryingBackoff complete · retry 2+1.0s
- ✓succeededCompleted in 142ms+1.2s
03 · Timing
Flexible
Immediate, delayed, or on a schedule — same queue model.
send-welcome-email
notifications · schedule
Now
14:20
Today
18:00
Tomorrow
09:00
Friday
18:00
Mode
immediate
Run at
14:20
Queue
notifications
04 · Visibility
Observable
Timeline, worker, duration, and failure detail per attempt.
send-welcome-email
job_88a910 · notifications
- 14:20:01queued
- 14:20:01started
- 14:20:02worker wrk_04a1
- 14:20:03completed · 142ms
Execution
See every attempt.
Know what happened.
Timeline
- ⋯queuedQueued14:29:01.004—
- ⟳runningStarted14:29:01.01886ms
- ✓succeededCompleted14:29:01.186168ms
Payload
{
"userId": "usr_99182",
"template": "welcome_onboarding"
}Failure handling
When things fail,
JobOrc keeps going.
dispatch-webhook
delivery_8f21 · attempt 2 / 3
- ⟳running
Attempt started
14:29:02.104
- ✕failed
Worker returned 503
+96ms
- ⟲retrying
Retry scheduled
+1.0s
- ✓succeeded
Delivery recovered
+1.2s
SDK
Three lines of code.
await joborc.jobs.enqueue(
"send-email",
{ userId }
)- Queued
- Running
- Succeeded