CONDOR_CONTINUE(1)

📦
version 25.14.1 · 12 versions
, in fedora 43

💖 CONDOR_CONTINUE(1) — the HTCondor Manual page, bestie edition 💖

okay so you suspended a job with condor_suspend and now you're sitting there like 🥺 bestie it's still frozen?? yeah. that's a whole mood. this page is your un-freeze button, and I'm gonna walk you through it like we're texting at 2am.

It lives in the HTCondor Manual, and it's called condor_continue. 💅

✨ NAME ✨

condor_continue — HTCondor Manual

Continue suspended jobs from HTCondor. That's it. That's the whole job. Iconic behavior honestly. 🎀

🌸 SYNOPSIS 🌸

condor_continue [-help | -version]

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

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

three whole ways to run it, pick your fighter ⭐

🦋 DESCRIPTION 🦋

condor_continue continues one or more jobs that have been suspended as a result of running condor_suspend. like, the jobs got put in timeout and now you're the one saying "okay you can come back 🫶".

The job(s) to be continued are identified by one of the job identifiers, as described below. 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 continue the job. so no, you cannot just go un-suspend your roommate's jobs. that's not your business, that's not your job, that's not your era. ✋

👑 OPTIONS 👑

  • -help — Display usage information. the "wait what do I do" button 💖
  • -version — Display version information. who dis, what build 🌈
  • -long — Display result ClassAd.
  • -totals — Display success/failure totals. the receipts ✨
  • -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.
  • -constraint expression — Continue all jobs which match the job ClassAd expression constraint.
  • -all — Continue all the jobs in the queue. every single one. no survivors. 💀
  • cluster — Continue all jobs in the specified cluster.
  • cluster.process — Continue the specific job in the cluster.
  • user — Continue all 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 — specify or don't, but it's always somebody's schedd getting the message. no cap. 🎯

⭐ EXIT STATUS ⭐

  • 0 — Success
  • 1 — Failure has occurred

vibe check passed or vibe check failed, there is no in between 😭

🌈 EXAMPLES 🌈

To continue a specific job:

$ condor_continue 432.1

To continue all jobs except for a specific user:

# condor_continue -constraint 'Owner =!= "foo"'

see how the second one uses #? iykyk. 🔥

💜 SEE ALSO 💜

condor_suspend, condor_rm, condor_hold, condor_release, condor_vacate_job, condor_vacate

the whole friend group fr fr 🫶

🌸 AVAILABILITY 🌸

Linux, MacOS, Windows

everywhere bestie, we are everywhere ✨

🎀 AUTHOR 🎀

HTCondor Team

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.

and that's the whole page!! go un-suspend your jobs, you absolute main character 👑

HTCondor Manual · drop date Oct 16, 2026 · CONDOR_CONTINUE(1) · mwah 💋

📦 where this page comes from