Apragya AI shows specific error codes when something goes wrong. Here are the ones you'll see most often, what they mean, and what to do.
403 Forbidden
Your role doesn't have permission for this action. Sometimes also a plan-feature gate. See role-cant-see-screen for the full breakdown.
404 Not Found
The record/page you're trying to open doesn't exist - either it was deleted, you have the wrong URL, or you don't have permission to see it (the platform sometimes returns 404 instead of 403 to avoid leaking record existence).
429 Too Many Requests
Rate-limited. Your tenant has hit its API rate limit. Slow down and retry in a minute. If it persists, your plan may need a bump or you have a runaway script hitting the API.
429 no_allocation_assigned
Specific to AI Credit usage - your account doesn't have an AI Credit allocation assigned. Ask your Org Admin to give you one (Admin > Users > [you] > AI Credits).
500 Internal Server Error
Something genuinely broke on our side. The platform automatically reports it to our error tracker; you don't need to file anything UNLESS it keeps happening. If it does, file a ticket with the URL + what you were doing.
503 Service Unavailable
A backend service is overloaded or briefly unavailable. Usually transient. Check status.apragya.ai for known incidents.
504 Gateway Timeout
A backend request took longer than the gateway's timeout. Usually safe to retry; if a specific action consistently 504s, file a ticket - that's a real bug to fix.