Docs / Troubleshooting
Troubleshooting
Symptom: 401 AUTH_REQUIRED on every request.
Cause. The Authorization header is missing or malformed.
Fix. Send `Authorization: Bearer <key>` exactly. The key must start with `tfp_test_` or `tfp_live_`.
Symptom: 403 AUTH_IP_BLOCKED from a server you trust.
Cause. The IP allowlist on the key does not include the egress IP of your service.
Fix. Edit the key in the portal and add the CIDR. The change takes effect within 60 seconds.
Symptom: 429 FETCH_RATE_LIMITED on the first request after a long idle period.
Cause. The per-minute window is full from a previous burst.
Fix. Wait for the window to roll over (X-RateLimit-Reset header) before retrying. Implement backoff in the client.
Symptom: 404 FETCH_NOT_FOUND for a key you just created.
Cause. Key creation is eventually consistent; the cache may not have updated.
Fix. Wait 5–10 seconds and retry. The portal dashboard shows the key as active immediately, but the gateway refreshes on a timer.
Symptom: 402 FETCH_QUOTA_EXCEEDED at the start of a billing cycle.
Cause. Credits from the previous cycle rolled over; the new month starts at 0.
Fix. Buy a credit pack, or upgrade your plan. Quota resets on the first day of the month UTC.
Still stuck?
Open a ticket from the portal with the requestIdfrom the error envelope. Support responds within 1 business day for free tier and 4 hours for business tier.