Under the hood
Useful2 Signal3
The cloud work bridge retries leftover jobs from a previous run and tracks busy sessions.
What's wrong with this entry?
Anonymous. No account, no email.
What
The component that hands cloud work to sessions now re-queues jobs left over from a previous run through its own retry loop, reports when a re-queue has to be dropped, and notifies callers whenever the number of busy sessions changes.
Details
- Startup re-queues are supplied as a separate input from ordinary work and get their own retry loop and drop telemetry.
- A busy-change callback fires when the set of busy sessions grows or shrinks.
- A poll result of "aborted" now shuts the bridge down cleanly instead of continuing.
Evidence
y("bridge_shutdown_requeue", "requeue_dropped")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.