A remote task stuck waiting on input now fails as blocked and tells you where to answer it.
tengu_coral_anchor Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.239: off
Read once, for one account on one subscription tier, against v2.1.239. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
A remote session that keeps asking for something this session cannot answer is now marked failed as "blocked" rather than polling forever, and you are told to answer it in the cloud or relaunch with a permission mode that does not prompt. The gate tengu_coral_anchor defaults to true in the build, so this is live unless remote config turns it off.
- Stalls are counted only when the remote session reports it requires action and no permission answer is already in flight.
- The threshold is 3 consecutive stalls, raised to 15 once this session has successfully forwarded an answer at least once.
the cloud session is waiting on input (a question, or a permission prompt this session couldn't answer for it).
Strings lifted out of the shipped bundle, so the claim above can be checked against them.