Troubleshooting
Start with the symptom you can see. Each guide explains the settings or API behavior to check next.
Checkout and catalog
| Symptom | Where to start |
|---|---|
| No shipping methods are returned | Check the checkout channel and shipping configuration |
| A product or variant is unavailable | Check checkout availability, then product troubleshooting |
| A paid checkout has not become an order | Review checkout completion |
| Checkout requests are slow | Review checkout performance guidelines |
| Channel behavior is unexpected | Channel troubleshooting |
API access and integrations
| Symptom | Where to start |
|---|---|
| A request fails with an authorization or permission error | Authentication and permissions |
| A GraphQL operation returns errors | API error handling |
| An app cannot install or connect | App troubleshooting |
| An app reports a specific error code | App error codes |
| A webhook is not behaving as expected | Webhook troubleshooting |
A docs example will not run
- Check that the Playground URL is your store’s API endpoint, ending in
/graphql/. - Check the editable Variables, including the channel slug. Replace placeholders with values from your store.
- In the API walkthrough, complete prerequisite examples in order. Changing an earlier step resets dependent progress.
- Read both the HTTP status and GraphQL
errorsin the response. A successful HTTP request can still contain GraphQL errors. - Compare your store’s Saleor version with the schema version shown in the API reference.
The embedded Playground sends public requests. Use a separate GraphQL client for operations that require an app token.
Still stuck?
Report a documentation issue and include the page URL. Describe what you expected, what happened, and the Saleor version. Include a minimal example with tokens and personal data removed.
For questions about your implementation, ask the Saleor community or join Discord.