Queued Audit Handling
How ConfigSentry handles queued audit submissions and what the visible audit statuses mean.
1. Why an Audit May Be Queued
Some audits can start immediately, while others may wait briefly before processing begins. ConfigSentry may queue an audit when workers are already busy or when concurrency or health checks delay a new start.
A queued state does not mean the submission was rejected. It means the audit was accepted and is waiting for worker capacity.
2. How Queued Audit Data Is Handled
Where an audit is queued, submitted configuration data or a prepared audit payload may be held temporarily in protected form until processing begins or the pending request expires.
- Temporary processing data is removed when processing completes or the pending request expires.
- ConfigSentry fails safely if the protected material needed to start processing is unavailable.
- Internal storage and cryptographic mechanisms are not described in this public guide.
3. What Each Status Means
- Queued - the audit has been accepted and is waiting for worker capacity.
- Running - a worker is actively processing the audit.
- Completed - the audit finished successfully and the report is available.
- Failed - the audit did not complete successfully.
- Retry Required - the audit could not be started or completed safely and needs a new submission or collection attempt.
- Expired - the queued audit was not processed before its queue expiry window ended.
- Cancelled - the queued audit was cancelled before completion.
4. What Retry Required Means
If a queued audit shows Retry Required, protected processing material was unavailable or the audit could not continue safely. The pending request is not processed with weakened protection.
The usual next step is to submit the manual upload again or allow the collector or retrieval workflow to collect the configuration again.
5. Which Workflows Can Show Queued Statuses
The same queue-related statuses can appear across multiple workflows:
- Manual configuration uploads
- Manual direct SSH audits
- Scheduled direct SSH audits
- Collector-based submissions
6. What This Does Not Mean
- A queued audit does not mean your firewall was changed.
- A queued audit does not mean the platform has weakened its normal protection for temporary processing data.
- A retry-required audit does not necessarily indicate a problem with your FortiGate itself.