Home › DevOps › AutoSys Box Stuck in RUNNING After Its Jobs Finished (ON_HOLD Child, box_success)
Intermediate 3 min · November 21, 2026

AutoSys Box Stuck in RUNNING After Its Jobs Finished (ON_HOLD Child, box_success)

An AutoSys box completes only when every child completes.

N
Naren Founder & Principal Engineer

20+ years shipping production infrastructure and CI/CD at scale. Drawn from code that ran under real load.

Follow
✓ Production
production tested
November 21, 2026
last updated
2,136
articles · all by Naren
Before you start⏱ 7 min
  • ✓AutoSys JIL basics
  • ✓AutoSys box jobs
 ● Production Incident 🔎 Debug Guide
⚡Quick Answer
  • A box completes when every child completes.
  • autorep -J BOX lists every child and its status; look for OH, AC or RU.
  • ON_HOLD child: box stays RUNNING until it's released (JOB_OFF_HOLD).
  • ON_ICE child: skipped, the box can complete.
  • Child waiting on a condition outside the box that never comes true: stays ACTIVATED.
  • For jobs that may legitimately not run, define box_success (and box_failure).
✦ Definition~90s read
What is AutoSys Box Stuck in RUNNING?

An AutoSys box job stays RUNNING until all of its child jobs have completed (or its box_success / box_failure condition is met). A child that is ON_HOLD, or ACTIVATED and waiting on a condition that won't be satisfied, keeps the box running indefinitely.

★
A box is a group trip: the bus doesn't leave until everyone's back.
Plain-English First

A box is a group trip: the bus doesn't leave until everyone's back. One person told to wait in the lobby (ON_HOLD) keeps the whole bus parked. Someone marked as not coming (ON_ICE) doesn't.

DAILY_BOX ran for five hours while every job the operator checked showed SUCCESS. A fourth child had been put on hold during an incident and never released.

How a Box Completes

A box finishes when all children have completed, unless box_success or box_failure says otherwise.

autorep.shBASH
1
2
3
4
5
6
autorep -J DAILY_BOX
# DAILY_BOX   RU
#  LOAD       SU
#  XFORM      SU
#  PUBLISH    SU
#  ARCHIVE    OH   <- holds the box
🎯 Key Takeaway
Every child counts.

ON_HOLD vs ON_ICE Children

A held child is still pending, so the box waits. An iced child is skipped for this run, so the box can complete.

release.shBASH
1
sendevent -E JOB_OFF_HOLD -J ARCHIVE
🎯 Key Takeaway
Hold blocks the box; ice doesn't.

Conditions That Never Come

A child whose condition depends on a job outside the box that didn't run stays ACTIVATED, and so does the box.

cond.shBASH
1
2
autorep -J ARCHIVE -q | grep condition
# condition: s(EXT_FEED)
🎯 Key Takeaway
Check child conditions.

Define When the Box Is Done

For children that may legitimately not run, set box_success so the box's success depends only on the jobs that matter.

box.jilJIL
1
2
update_job: DAILY_BOX
box_success: s(LOAD) & s(XFORM) & s(PUBLISH)
🎯 Key Takeaway
box_success redefines done.
● Production incidentPOST-MORTEMseverity: high

The Child Nobody Released

Symptom
LOAD, XFORM and PUBLISH were SU; DAILY_BOX stayed RU.
Assumption
The operator checked the three jobs they knew about and assumed the box was hung.
Root cause
ARCHIVE, a fourth child, had been put ON_HOLD during an earlier incident and never released. A box waits for every child.
Fix
sendevent -E JOB_OFF_HOLD -J ARCHIVE; it ran, and the box completed. A check for long-held jobs was added to the morning runbook.
Key lesson
  • Run autorep on the box, not on the jobs you remember.
  • ON_HOLD children hold the box.
  • Track who holds what.
Production debug guideWhich child is holding it?3 entries
Symptom · 01
Box RU, children SU
→
Fix
autorep -J BOX: look for a child in OH, AC or RU.
Symptom · 02
Child in AC for hours
→
Fix
Check its condition: it may depend on a job that didn't run.
Symptom · 03
Optional child shouldn't block the box
→
Fix
Set box_success on the box.
⚙ Quick Reference
4 commands from this guide
FileCommand / CodePurpose
autorep.shautorep -J DAILY_BOXHow a Box Completes
release.shsendevent -E JOB_OFF_HOLD -J ARCHIVEON_HOLD vs ON_ICE Children
cond.shautorep -J ARCHIVE -q | grep conditionConditions That Never Come
box.jilupdate_job: DAILY_BOXDefine When the Box Is Done

Key takeaways

1
Box waits for every child.
2
autorep -J BOX shows all children.
3
ON_HOLD blocks; ON_ICE doesn't.
4
Unmet conditions keep children ACTIVATED.
5
box_success for optional jobs.

Common mistakes to avoid

3 patterns
×

Checking only known children

Symptom
Can't see what holds the box.
Fix
autorep -J BOX.
×

Forgetting held jobs

Symptom
Boxes stuck days later.
Fix
Release or ice, and track holds.
×

Optional jobs with no box_success

Symptom
Box waits for a job that may never run.
Fix
box_success.
INTERVIEW PREP · PRACTICE MODE

Interview Questions on This Topic

Q01SENIOR
Why would an AutoSys box stay RUNNING when its jobs succeeded?
Q01 of 01SENIOR

Why would an AutoSys box stay RUNNING when its jobs succeeded?

ANSWER
A child is ON_HOLD or waiting on an unmet condition; a box waits for every child unless box_success says otherwise.
FAQ · 2 QUESTIONS

Frequently Asked Questions

01
Why is my AutoSys box still running?
02
Does an ON_ICE job stop the box completing?
COMPLETE GUIDE
The Complete AutoSys Workload Automation Guide for Engineers →

JIL syntax, sendevent, autorep, box jobs, file watchers, scheduling, HA, security, cloud workload automation, and 22 interview questions — the definitive AutoSys reference for production engineers.

N
Naren Founder & Principal Engineer

20+ years shipping production infrastructure and CI/CD at scale. Drawn from code that ran under real load.

Follow
✓ Verified
production tested
November 21, 2026
last updated
2,136
articles · all by Naren
🔥

That's AutoSys. Mark it forged?

3 min read · try the examples if you haven't

←
Previous
AutoSys max_run_alarm and term_run_time: Alert on Long-Running Jobs
51 / 51 · AutoSys
Next
Introduction to Jenkins
→