# Fail work that cannot meet its useful deadline

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

---

## Fail work that cannot meet its useful deadline

ID: MHC-D-RESEARCH-0538 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/fail-work-that-cannot-meet-its-useful-deadline

Late work can consume real resources while producing zero useful result.

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

### Use when

- A request has waited so long that continuing to process it cannot meet the caller's deadline or service objective.

### Avoid when

- Some durable background jobs remain valuable after the requester waits; distinguish user deadlines from durable obligations.

### Explanation

Propagate deadlines into the processing path. Before starting or continuing expensive work, check whether enough time remains to deliver a useful result. If not, fail quickly or return an explicit degraded response so resources can serve work that still has a chance to succeed.

### Example

Do not run a 30-second analysis when only two seconds remain before the user request times out.

### Check

The system stops spending material work on requests that are already unable to create timely value.

### Limits

- Some durable background jobs remain valuable after the requester waits; distinguish user deadlines from durable obligations.

### Evidence and sources

- supports: Fail-fast strategies release resources when a request cannot succeed within the required service objective instead of allowing doomed work to continue consuming capacity. — RS-D6954C8ACF093D83. Failing fast is inappropriate when partial or delayed completion still has required value. (Fail fast desired outcome)
- 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-D6954C8ACF093D83: REL05-BP04 Fail fast and limit queues — https://docs.aws.amazon.com/wellarchitected/latest/framework/rel_mitigate_interaction_failure_fail_fast.html
- RS-C1BEE49CF0075A87: Addressing Cascading Failures — https://sre.google/sre-book/addressing-cascading-failures/

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/open-the-circuit-when-a-dependency-keeps-failing
