You'll notice
Useful2 Signal3
Automatic artifact replies now report a usage limit instead of retrying blindly.
What's wrong with this entry?
Anonymous. No account, no email.
What
The background job that composes automatic replies and edits on artifacts used to fold every API error into one generic failure and retry. It now recognises a usage-limit response and reports it as its own declined outcome instead.
Details
- The usage-limited case surfaces as a declined status rather than a generic compose failure headed for retry.
- Other API errors keep the previous generic-error-and-retry behaviour.
Evidence
compose_usage_limited
Strings lifted out of the shipped bundle, so the claim above can be checked against them.