Principle

Fail work that cannot meet its useful deadline

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

See the ideaAn illustrative example

Can the result still arrive usefully?

Original Vedokrok holds an unprinted programme beside a fictional theatre hatch with a SHOW ENDED card and a separate archive folder
A programme meant for people entering a performance has a useful time window. Before expensive work continues, check whether its intended result can still help.

Follow the image, then make a version for your own work.

What value remains after the waiting limit?

Explore either choice, then decide what fits your situation.

Check my useful deadline

Stays on this page. Copy or save before leaving. Keep sensitive details out.

Fill each field to make your note.

A requester’s waiting limit does not cancel a durable obligation. Delayed records, background work or partial results may still have required value; keep those purposes distinct.

Read the idea Save this pictureVedokrokSee the idea. Make your next move.

Before you use it

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

Keep this limit in mind

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

Why it matters

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.

An example

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

Check your result

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

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading
Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingFail work that cannot meet its useful deadline

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.

Failing fast is inappropriate when partial or delayed completion still has required value.

REL05-BP04 Fail fast and limit queues · 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.

Bursty asynchronous workloads can legitimately benefit from larger queues when backlog remains useful.

Addressing Cascading Failures · Queue management and latency/deadlines

All sources (2)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details