mc inventory resume

mc inventory resume resumes a suspended inventory job.

The job transitions back to its pre-suspension state.

This command requires the admin:InventoryControl permission.

Syntax

Parameters

TARGET/BUCKET

Required

The full path to the bucket containing the inventory configuration. Specify both the alias and bucket name in the format ALIAS/BUCKET.

For example:

mc inventory resume myaistor/mybucket weekly-report

INVENTORY-ID

Required

The unique identifier of the inventory job to resume.

For example:

mc inventory resume myaistor/mybucket monthly-inventory

Global flags

This command supports any of the global flags.

Examples

Resume a suspended job

The following command resumes a suspended inventory job:

mc inventory resume myaistor/mybucket suspended-job
  • Replace myaistor with the alias of your AIStor deployment.
  • Replace mybucket with the name of the bucket.
  • Replace suspended-job with the inventory configuration ID.

The job transitions back to its pre-suspension state and resumes normal operation.

S3 compatibility

The mc commandline tool is built for compatibility with the AWS S3 API and is tested with AIStor and AWS S3 for expected functionality and behavior.

MinIO provides no guarantees for other S3-compatible services, as their S3 API implementation is unknown and therefore unsupported.

While mc commands may work as documented, any such usage is at your own risk.

Permissions

The user or service account running this command must have the admin:InventoryControl permission.

For more information on AIStor policies and permissions, see Access Management.

Behavior

State restoration

AIStor stores the job’s current state during the suspension process. When you resume a job, it transitions from to its pre-suspension state.

Suspension State Resume State
Running Pending
Pending Pending
Sleeping Sleeping
Failed Failed
Canceled Canceled

Suspended jobs

AIStor supports indefinite job suspension.

Resuming a long-suspended job has the following behaviors:

  • One-time jobs: Execute immediately (if they were Pending/Running) or follow retry timing (if Failed)
  • Periodic jobs: Resume normal scheduling; no execution of missed runs

The scheduler does not run missed executions for periodic jobs. For example, suspending a daily job on Monday and resuming it on Friday does not result in AIStor running the missed Tuesday-Thursday executions.