What
Status objects for timed or capped remote/background operations now include a new open field:
- A status object used for tracking timed/capped operations now sets
open: "stalled"when a request isn't a probe and hasn't been 'taken back,' in addition to its existing taken-back-based branching. - A
still_runningstatus response now includesopenset to either"still_running"(when the operation is literally still running) or"delivery_unknown"otherwise, alongside the existing code/message/host fields.
Why
This gives a clearer, explicit signal for distinguishing an operation that's genuinely still running from one that's stalled or whose delivery status just isn't known, instead of leaving that ambiguous.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It's unclear which user-facing feature consumes this 'stalled' status or how it's surfaced.