# Push back on intake before the backlog becomes the outage

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Push back on intake before the backlog becomes the outage

ID: MHC-D-RESEARCH-0535 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/push-back-on-intake-before-the-backlog-becomes-the-outage

A growing queue is a message from capacity, not a storage success story.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- Work arrives faster than it can be completed and producers keep submitting at the same rate.

### Avoid when

- Backpressure needs clear user behavior; invisible throttling can look like random failure.

### Explanation

When consumers approach their sustainable limit, slow or reject new intake rather than allowing unbounded backlog growth. Propagate the pressure to the producer through quotas, concurrency limits, retry-after signals or explicit scheduling. The producer must see that capacity is constrained.

### Example

Limit new agent jobs when human review capacity is saturated instead of generating thousands of outputs that will expire unread.

### Check

Backlog pressure changes intake behavior before the system exhausts memory, deadlines or reviewer capacity.

### Limits

- Backpressure needs clear user behavior; invisible throttling can look like random failure.

### Evidence and sources

- supports: AWS's 2026 fairness guidance uses throttling, quotas and backpressure to prevent one workload from starving others in a shared system. — RS-264CB803462A1B86. Fairness policy must reflect actual priorities rather than equalizing workloads that have different importance. (Admission control and fairness)
- supports: Google SRE recommends small queues or early rejection under steady overload because long queues add latency, memory use and work that may already have missed its deadline. — RS-C1BEE49CF0075A87. Bursty asynchronous workloads can legitimately benefit from larger queues when backlog remains useful. (Queue management and latency/deadlines)
- RS-264CB803462A1B86: Fairness in multi-tenant systems — https://builder.aws.com/content/3Eupj3d2bo4fEvlzYbICMZNhQ3B/fairness-in-multi-tenant-systems
- RS-C1BEE49CF0075A87: Addressing Cascading Failures — https://sre.google/sre-book/addressing-cascading-failures/

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/give-shared-capacity-a-noisy-neighbor-rule
