Before provider execution
A request can be rejected for an invalid or revoked key, disabled account, insufficient balance, exceeded daily limit, too many pending requests, unsupported model or protocol, or an invalid payload. Fix the account or request condition before retrying.Fallback behavior
Aster may retry the one compatible fallback configured for the selected product and route. It does not run an open-ended cascade across expensive models. The gateway preserves one request identity and settles only the final billable outcome.Client retry guidance
- Do not retry authentication, balance, limit, or validation failures until the underlying condition changes.
- Use bounded backoff for transient service failures and retain the request identifier for support.
- Cancellation stops the active request path. Inspect the durable Usage record before retrying after a lost connection.
Failed and cancelled requests carry no customer charge. If a response outcome is unclear, check Usage before submitting the same expensive job again.