Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex AI Studio
    • About Yandex AI Studio
    • Yandex Workflows
    • Quotas and limits
    • Terms and definitions
  • Compatibility with OpenAI
  • Access management
  • Pricing policy
  • Audit Trails events
  • Public materials
  • Release notes
    • Error codes
    • Request headers for troubleshooting
  1. Troubleshooting
  2. Error codes

Error codes

Written by
Yandex Cloud
Updated at October 24, 2025

In response to any request, AI Studio models return a message containing a request processing code and status. If there is an error processing the request, the message will also include its possible cause.

When processing model responses in your app, refer to the request code and status. Error messages contain useful information, but may change with model updates.

gRPC REST Status Cause Solution
0 200 OK Operation completed —
3 400 INVALID_ARGUMENT Invalid request Check the request format. You may have specified an incorrect model URI, exceeded the prompt length, set an invalid parameter value, or failed to comply with the YandexART ethical guidelines.
For example, to resolve the invalid model_uri, Failed to parse model URI errors, check that you have entered the correct model URI and specified the folder ID.
An error of the Specified folder ID does not match with service account type means the folder ID is incorrect or the service account sending the request does not have access to the specified folder. Check which account you are sending the request from.
4 504 DEADLINE_EXCEEDED Request timed out Network issues between the client and server. Try again or contact support.
7 403 PERMISSION_DENIED Not enough permissions Make sure that the service account you are using to send your request has the required roles. If access to the model you selected is provided upon request, make sure you got it.
8 429 RESOURCE_EXHAUSTED Quota exceeded Depending on your quota, wait or contact support to increase your quota. When requesting a quota increase, specify the model, working mode, and the name of the quota to increase. Our support team may request additional information.
12 501 UNIMPLEMENTED Service-side issue Contact support.
13 500 INTERNAL Internal service error Contact support.
14 503 UNAVAILABLE Service unavailable Try again or contact support.
16 401 UNAUTHENTICATED Authorization error Check that you are using the correct account, API key, and IAM token, and that the token has not expired. Error messages may contain information about the error. For example, Unknown api key indicates the API key or its scope is incorrect, and The apikey has expired, the API key has expired.

Was the article helpful?

Previous
AI assistants
Next
Request headers for troubleshooting
© 2025 Direct Cursus Technology L.L.C.