flux update requests an update of one or more attributes for an active (pending or running) job. Updates are permitted and validated by the job manager before being applied to the job.

Keys are expressed as period-delimited strings corresponding to an attribute path in jobspec. If a key does not start with attributes., tasks., or .resources (the top-level jobspec keys allowed by RFC 14), then the key is assumed to be prefixed with attributes.system., such that:

$ flux update f12345 myattr="value"

would request an update of attributes.system.myattr to the string value "value".

The flux update command may also support other convenient key aliases. Key aliases are listed in the SPECIAL KEYS section below.

Updates will be sent to the job manager update service, which checks that the current user is permitted to apply all updates, and that all updates are valid. If multiple updates are specified on the command line, then all updates are either applied or the request fails.


Job updates are allowed in the job manager by special plugins on a case by case basis. At this time, the set of keys that can actually be updated for a job may be very limited.

The instance owner may be allowed to update specific attributes of jobs and bypass validation checks. For example, the duration of a guest job may be increased beyond currently configured limits if the update request is performed by the instance owner. When a job is modified in this way, future updates to the job by the guest user are denied with an error message:

job is immutable due to previous instance owner update

This is necessary to prevent possible unintended bypass of limits or other checks on a job by a guest.

The flux update command may also support special handling of values for specific keys. Those special cases are documented in the SPECIAL KEYS section below.


-n, --dry-run

Do not send update to job manager, but print the updates in JSON to stdout.

-v, --verbose

Print updated keys on success.


attributes.system.duration, duration

Updates of the job duration can take the form of of [+-]FSD, where + or - indicate an adjustment of the existing duration, and FSD is any string or number in RFC 23 Flux Standard Duration. Examples include 60, 1m, 1.5h, +10m, -1h. Updates to the duration of a running job may be allowed (instance owner only) and are handled as a special case. For details see DURATION UPDATE OF A RUNNING JOB below.

attributes.system.queue, queue

Updates of a pending job's queue to another enabled queue may be allowed. The update could be rejected if the new job exceeds the destination queue limits or if the job would not be feasible in the new queue.


Alias for job name, i.e. attributes.system.job.name


As a special case, an update of the duration of a running job may be allowed when performed by the instance owner and validated by the scheduler. When a running job's duration is updated, this triggers a resource-update event in the main eventlog which contains the updated resource set (R) expiration time. This event then triggers the following actions to propagate the updated job expiration through the system:

  • The updated expiration is forwarded to the job execution system which modifies its expiration timer for the job.

  • If the user enabled the job shell option to signal a job before the time limit, then the job shell receives the updated R and resets this timer.

  • If the job is a subinstance of Flux (e.g. started with flux-alloc(1) or flux-batch(1)), the instance resource module also receives notification of the updated R, replaces its internal copy, writes the update to resource.R in the KVS, and issues a resource-update event to the resource.eventlog.

  • The resource-update event in the eventlog results in a new RFC 28 resource.acquire response to the scheduler containing the updated expiration.

  • The instance scheduler accepts the new response and updates its internal resource set representation.

  • The update service in the job-manager is notified of the R update, and if the expiration has been increased, it walks the list of running jobs and issues a resource-update event for any job which had its expiration set based on the previous instance expiration.

  • For any job that has its expiration extended due to an instance expiration update, all these steps are repeated.



All updates were successful


Updates were invalid or not permitted, or the provided JOBID was invalid or inactive, or the user does not have permission to modify the job


Syntax or other command line error


Flux: http://flux-framework.org

Flux RFC: https://flux-framework.readthedocs.io/projects/flux-rfc


14/Canonical Job Specification


flux-jobs(1), flux-submit(1), flux-bulksubmit(1)