# Errors and workarounds

These are some common issues that you might face while running tests and how to get past them:

Network Error: This happens when the URL used in the test suite is not accessible. Verify that the URL is correct and check its accessibility using cURL. Make sure that the backend is running. Also, make sure that the domain part is not missing from the URL and that the protocol http/https is correct.
Timeout error: This happens when the API call times out. Currently, the timeout is 10s (we're planning to make this configurable in an upcoming release). If you don't expect the API to take this long, check the firewall/security groups on the test machine. In some cases, if a particular port/IP is not allowed to access the machine, the API call will simply get stuck and not return with any error.
Unexpected 404 error: If you get a 404 Not Found error where you expected the API call to work, check if the URL is correct. Check for extra/missing slashes in the URL. You can use the edit all tests feature to fix the URL for all tests in one go. An incorrect HTTP method might also result in this issue, so check if you accidentally entered the method as GET instead of POST, for example.
Unexpected 403/401 error: 403/401 are authentication/authorization errors. Check if the auth token is missing from the header or incorrect. Specifically, while using bearer auth along with variables, make sure you don't end up adding the "Bearer" keyword in both the header and variable or missing it from both. For example, if you set the header to {"Authorization": "Bearer {{token}}"} and then set the token variable as "Bearer some_token_value", this will result in an error as the "Bearer" keyword is present twice.
Unexpected 405 error: This error occurs when the request method (e.g., GET, POST, PUT, DELETE) is not supported by the endpoint you’re trying to access.