Snapshot Processing Limits
Forward Enterprise limits the number of snapshots that can be processed at the same time. This prevents large volumes of snapshot processing requests — such as those triggered by automated scripts or bulk reprocessing — from overwhelming the system and degrading responsiveness.
How It Works
Snapshot processing uses a concurrency limit with a queue:
- Concurrency limit (default: 8): Up to 8 snapshots can be processed simultaneously. Additional requests are placed in a first-in, first-out queue.
- Queue depth limit (default: 50): Up to 50 additional requests can wait in the queue. As in-progress snapshots complete, queued requests are automatically promoted and begin processing.
- Queue full: If the queue is full, new snapshot processing requests are rejected with an HTTP 429 (Too Many Requests) response. Rejected requests are not retried automatically and must be resubmitted after capacity becomes available.
These limits do not affect how fast the system processes individual snapshots. They control how many requests can be submitted and queued at a time. In most cases, Background Snapshots Reprocessing handles reprocessing needs automatically without reaching these limits.
Deployment Type Availability
| Deployment Type | Enabled by default |
|---|---|
| SaaS | Yes |
| Self-hosted | No |
On self-hosted deployments, these limits can be enabled and the concurrency and queue depth values can be adjusted to match the capacity of the deployment. Contact your Forward Networks representative for configuration details.