bankr-error-handling

Handling Bankr API 429 rate limit errors requires waiting for the rate-limit reset and retrying with exponential backoff. This approach diagnoses the 429 status, pauses automated job executions safely, and resumes requests only after the throttling window clears to prevent stalled workflows.

Bankr API 401 authentication errors occur when the BANKR_API_KEY is missing, malformed, or expired. Diagnosing this error requires verifying the key format and environment configuration, then escalating with a diagnostic report if the key needs rotation.

Troubleshooting Bankr API connectivity and timeout issues involves verifying the reachability of api.bankr.bot and applying retry with exponential backoff for transient network failures. This self-healing approach recovers dropped connections without manual intervention.

You can automatically recover Bankr API failures by diagnosing the exact cause and applying safe recovery actions. The system self-heals authentication, connectivity, and rate-limit issues autonomously, escalating to an operator with a diagnostic report only when backoff retries fail or key rotation is required.

You should escalate Bankr API errors when recovery attempts fail after exponential backoff or when authentication issues require key rotation. Escalating with a diagnostic report ensures operator intervention only for persistent failures, preserving automated job stability for transient issues.