The suggestion to turn a loop into a cloud schedule no longer needs its old experiment.
tengu_surreal_dali On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.251: not a boolean we can read
Read once, for one account on one subscription tier, against v2.1.251. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The prompt that suggests turning a session-local loop into a durable cloud schedule used to require the tengu_surreal_dali experiment. That name no longer appears anywhere in this build; the suggestion is now gated by two other checks combined with the existing remote-sessions policy check.
- The remaining conditions are the account policy allowing remote sessions and there being no existing schedules.
- What the two replacement checks test is not determinable from the build, so whether this is now on for everyone eligible or moved behind another gate is open.
## Offer cloud first
Strings lifted out of the shipped bundle, so the claim above can be checked against them.