Errors
The best BrowserBee integrations make clear distinctions between:
- authentication failures
- validation failures
- missing resources
- transient operational failures
- rate limiting and backpressure
Error handling principles
Use these rules by default:
- retry only transient failures
- surface validation failures to the caller or operator clearly
- log enough request context to debug quickly
- do not hide permanent errors behind generic retries
Error classes to plan for
Authentication and authorization
Treat these as configuration or credential problems first:
- wrong token
- revoked token
- wrong environment
- missing auth header
Validation failures
Treat these as request-construction problems:
- malformed payloads
- missing required fields
- invalid parameter values
These usually require code or input fixes, not retries.
Missing resources
Treat these as state mismatches:
- stale identifiers
- deleted resources
- environment drift
Transient operational failures
Treat these as candidates for bounded retries:
- timeouts
- temporary service disruption
- network interruptions
Logging guidance
Log:
- endpoint path
- environment
- status code or error class
- attempt count
- request correlation identifiers if you have them
Do not log tokens or sensitive payload data.
Next steps
- Review HTTP methods.
- Review Handle rate limits and retries.