CONDOR_RELEASE(1)

💖 condor_release — the HTCondor manual page, bestie edition 💖

okay so this is the condor_release(1) page from the HTCondor Manual, and it's literally about changing held jobs back to idle. that's it. that's the whole vibe. let's go ✨

---

🌸 NAME 🌸

condor_release — HTCondor Manual

Change held jobs back to idle. 🦋

---

✨ SYNOPSIS ✨

condor_release [-help | -version]

condor_release [OPTIONS] [cluster... | cluster.proc... | user...]

condor_release [-debug] [-long] [-totals] [-all] [-reason message]
[-constraint expression] [-pool hostname[:portnumber] | -name scheddname
| -addr "<a.b.c.d:port>"]

---

🎀 DESCRIPTION 🎀

so basically, condor_release releases job(s) from the held state back to idle in HTCondor, which lets the job(s) get matched to resources and actually, you know, executed. the whole point. the dream. 🔥

but here's the tea: for any given job, only the owner of the job or one of the queue super users (defined by the QUEUE_SUPER_USERS macro) can release the job. no random people in your business, periodt. 💅

---

🌈 OPTIONS 🌈

• -help — display usage information. the "what do i even do here" button 🫶
• -version — display version information. the "who am i" button ⭐
• -long — display result ClassAd.
• -totals — display success/failure totals. the receipts, basically 🧾
• -pool hostname[:portnumber] — specify a pool by giving the central manager's host name and an optional port number. 📍
• -name scheddname — send the command to a machine identified by scheddname.
• -addr "<a.b.c.d:port>" — send the command to a machine located at "<a.b.c.d:port>".
• -debug — causes debugging information to be sent to stderr, based on the value of the configuration variable TOOL_DEBUG. 👀
• -reason message — sets the ReleaseReason attribute to the provided message in the job(s) ClassAd.
• -constraint expression — release all jobs which match the job ClassAd expression constraint.
• -all — release all the jobs in the queue. all of them. every last one 👑
• cluster — release all jobs in the specified cluster.
• cluster.process — release the specific job in the cluster.
• user — release jobs belonging to specified user.

---

💜 GENERAL REMARKS 💜

if the -name option is specified, the named condor_schedd is targeted for processing. otherwise, the local condor_schedd is targeted. so like, no -name, no travel, we stay home 🏠

a job can be put on hold by the user who submitted the job, the AP administrator(s), or by HTCondor when something went wrong during the job's attempt to run. (not me getting held by the universe 😭)

⚠️ attempts to release a job not in the held state will result in a failure and the job will be unchanged. so don't try it. the job said "i'm not held" and it meant it 💀

---

🦋 EXIT STATUS 🦋

• 0 — Success ✅
• 1 — Failure has occurred ❌

---

🍓 EXAMPLES 🍓

to release a specific held job:

$ condor_release 432.1

release all held jobs for user Mary:

# condor_release mary

---

🔥 SEE ALSO 🔥

condor_hold, condor_rm, condor_continue, condor_suspend, condor_vacate_job, condor_vacate

the whole friend group honestly 💖

---

⭐ AVAILABILITY ⭐

Linux, MacOS, Windows — every platform, she's everywhere 🌍✨

---

👑 AUTHOR 👑

HTCondor Team

---

🎀 COPYRIGHT 🎀

1990-2026, Center for High Throughput Computing, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI, US. Licensed under the Apache License, Version 2.0.

---

okay and that's the whole page, no cap 💅 this was the HTCondor Manual version dated Oct 16, 2026 — go release those held jobs bestie, you got this 🫶🌸✨