> ## Documentation Index > Fetch the complete documentation index at: https://docs.stackone.com/llms.txt > Use this file to discover all available pages before exploring further. # Debug & Monitor > Diagnose failing calls and watch usage. When a tool call fails or returns nothing, start with the [Request Logs](https://app.stackone.com/request_logs). They show every request to StackOne and the underlying calls StackOne made to the provider, filterable by account, provider, status, and date. Logs are kept for 90 days. Click a log entry to see request and response headers, body, and status, plus the **Underlying Requests** tab for the provider-side calls. ## Common errors | Symptom | Likely cause | Fix | | - | - | - | | `401` / `403` | Bad API key encoding, or `x-account-id` from a different project | Re-check Basic auth encoding and that the account belongs to your project | | Empty tools list | No actions enabled, or account inactive | Enable at least one action in the connector config; confirm the account is active | | `400` missing `x-account-id` | Client can't send custom headers | Pass `?x-account-id=` as a query param | | `406 Not Acceptable` | Missing `Accept` header | Send `Accept: application/json, text/event-stream` | | Tool execution fails | Bad params, provider error, or rate limit | Validate params; check the underlying request in logs | See [MCP Troubleshooting](/embed/call-actions/mcp/troubleshooting) for full error codes and diagnostics. ## Rate limits API keys are limited to **1000 requests per minute**. Over the limit returns `429 Too Many Requests` with a `Retry-After` header (in seconds). Read it and back off before retrying. StackOne automatically retries provider-side 429s (up to 5 attempts, within a 60-second request lifetime) using the provider's `Retry-After`. See [Rate Limiting](/platform-api/rate-limiting). Check for active incidents This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.