Start here
☁️ Your Xano Account
Special Discount Pricing
How to troubleshoot issues building in Xano, and how to get the best possible support.
At Xano, we are always happy to help troubleshoot an issue, but understand that sometimes when issues arise, it could be outside of normal business hours or time zone differences make it difficult to provide real time support. There are a few methods you can use to narrow down the source of a problem and potentially solve it on your own before reaching out to support.

Debugging Performance Issues

502 errors when calling APIs or otherwise experiencing slow performance typically means that you are maxing out your instance resources. This means you should consider ways to increase performance. It is almost impossible to make a strict determination on “what package do I need” because everyone’s logic and data volume is different.
There are several variables to look at when addressing performance issues, including:
  • The volume of API requests and the time between them
  • The complexity of the business logic
  • The amount of data being sent/received.
[Note: If your instance hits maximum usage, reported statistics may no longer be accurate.]
Start by taking a look at your API request history to search for any endpoints that are taking longer than expected. As a good rule of thumb, any request that the user has to wait for should be no longer than 5 seconds. Things that are processing more data should be moved to a background task and cached for a user to view it later.
To view the request history and sort by duration, head over to your workspace dashboard and click Details next to API requests, and you can easily filter by a time you specify.
Accessing the Request History
To address slower performance, you should also consider applying a database index. An index allows you to quickly search through a table by specifying the field or fields you are searching on, without searching the entirety of every record. This type of performance issue is typically identified by high database load in the resource graph on your dashboard.
In addition to indexing, data caching features are a robust solution for faster response times. Please check your Xano plan for availability of these features. More on those here.
If you have already addressed efficiency concerns in your database and function stacks, the next step is to upgrade your Xano plan for improved performance.

Debugging Errors in your Endpoint

There are two key features for debugging errors: the Debugger and the Stop & Debug utility function. The Debugger allows you to see the output of each step and any variables that are referenced during the run. The Stop & Debug function allows you to halt the function stack at any point and output the value of a specified variable.
In this example endpoint, an external API call is being made and the resulting data is being stored as a new record in the database.
Example of an endpoint that will return an error
Upon running this endpoint, the following error occurs.
The error that occurs when running the example endpoint
The endpoint is unable to locate the variable of api_1.message. To solve this problem, we need to check the contents of api_1 and make sure that we have implemented dot notation (the path to api_1.message) correctly. We can do this either by viewing the debugger and looking at the contents of the variable, or by using Stop & Debug to show the output of the api_1 variable.
Using the Debugger to view the response
Using Stop & Debug to view the response
In either of these methods, we can see that our path should actually be as follows:

If you have a successful run in Xano, but not from an external call…

Utilizing API request history to simulate a failed run is key to understanding why your API calls may be failing. You can copy the input from an external request and use it in the debugger to see the full response of each step in your function stack through a normal Run & Debug.

Contacting Support

To receive the most efficient experience possible, please make sure you have addressed the following before reaching out to Xano support:
  • Have you tried the debugging steps listed above to narrow down problematic requests or steps in your function stack?
  • If you are having an issue on your front-end, have you taken the necessary steps to ensure that everything is set up correctly on your front-end to use external data sources (like Xano)?
  • Have you consulted the Xano community and the documentation on this issue?
If you have taken the steps to troubleshoot your endpoint, or you’ve received an Unknown Error Occurred message, and you need to reach out to support for assistance, please make sure that you provide as much of the following information as possible.
  • Any screenshots of error messages you see
  • A screenshot of your browser's developer console when the issue occurs
  • Steps to reproduce the issue, if any
  • What front-end you are using
  • Any inputs required to run
  • A link to the endpoint, function, task, or database trouble you are having an issue with. Please provide the URL in your address bar, not the endpoint URL you use with your front-end.
If you do not provide all of the information listed above, your support request will likely receive a delayed response.