HashiCorp Nomad

• Job failedRuns when a job ends because it failed, such as a batch job, a periodic job's run or a dispatched job that exited with an error, with its failed allocations and what they printed last. Or when any job ends, finished or stopped too. Jobs already ended when the workflow is turned on don't start it.
• Allocation failedRuns when an allocation (a copy of a job on a node) fails, after Nomad's own restarts, or is lost with its node, with the task that failed and its last message. Allocations already failed when the workflow is turned on don't start it.
• Deployment failedRuns when a job's deployment (a rolling update to a new version) fails, such as when new allocations don't become healthy in time, with Nomad's reason and each task group's healthy and unhealthy counts.
• Node went downRuns when a node (a client machine) stops answering Nomad and is marked down or disconnected, such as to page someone. Nodes already down when the workflow is turned on don't start it.

• List jobsList the jobs in the connection's namespace with their status and how many allocations are running or failed, such as for a status report, or only those with a status or type.
• Get job statusSee how a job is doing: its status and version, each task group's running and failed allocations, and its latest deployment.
• List job allocationsList a job's allocations (the copies of it Nomad placed on nodes), newest first, with the node each is on, its status and how each task is doing, or only those with a status, such as failed.
• Run jobSubmit a job file to Nomad, like nomad job run: a new job starts, and a changed one is updated (rolling out as its update block says). The file is HCL, or the job's API JSON.
• Dispatch jobStart a run of a parameterized job, such as a report or a backup, with a payload and meta values for it to use.
• Run periodic job nowStart a run of a periodic job now rather than at its next scheduled time, such as a backup before a change.
• Stop jobStop a job: Nomad stops all its allocations. A stopped job can be run again; purging also removes it and its history from Nomad for good.
• Scale task groupChange how many copies of a job's task group Nomad runs, such as more web servers for a sale, or 0 to pause it.
• Restart allocationRestart a running allocation's tasks where they are, such as to pick up a changed setting, or only one task.
• Stop allocationStop one allocation, such as a stuck one; Nomad places a new one for its job, on the same node or another.
• Get task logsRead the last lines a task printed, its output or its errors, such as to send with an alert when it fails.
• List nodesList the nodes (client machines) with their status, whether they are draining or take new work, and their working drivers, or only those with a status, such as down.
• Drain nodeDrain a node before maintenance, such as a reboot: Nomad moves its allocations to other nodes and places nothing new on it. Or stop a drain.
• Set node eligibilityStop Nomad placing new allocations on a node, leaving what runs there alone, or let it place them again.
• Get variableRead a Nomad Variable's keys and values, such as an app's settings, to use in a later step. One that isn't there comes back with found false rather than failing the step. The values are in the step's result, so anyone who can see this workflow's runs can see them.
• Put variableSet keys of a Nomad Variable, such as a new database address for jobs to read, creating it if it isn't there. Other keys stay unless 'Replace every key' is on.
• Delete variableDelete a Nomad Variable and all its keys. Nomad keeps no history, so it can't be brought back.

No actions match that.