Fix a request that does not work
What common errors mean, why a button or history is missing, and who decides access.
In short
Most problems are one of three things: the request reached the API and was refused, it never reached the API, or you lack access to a button or project. This guide lists what each error means and what to check, in the order to check it.
Before you start
- Who: anyone. Several fixes need Edit or Manage on the project; the steps say which.
- Plan: every plan; Plan & usage shows what your plan includes.
- First: note the exact message you see.
Steps
- Check that you are signed in, and in the workspace the project belongs to.
- Open Settings, "Plan & usage": does your plan include the feature, and is there capacity left?
- Point at the "Visible to" mark beside the project's name: its hint says what you can do there - view, comment, run, edit or manage.
- Compare it with what the action needs: running needs Run, changing requests and suites needs Edit, environment settings, sharing and ways in need Manage. Running against Production at the Run level needs the project's switch.
- Ask for more access from the project, or ask whoever manages it.
All of these apply together. A plan that includes load testing still needs Edit on the project to start one, and a share never gives more than your organization role allows.
The request did not work
A call that never completed has no status code, but it is still kept as a run. Requests go out from the {{brand}} server, not your computer, so that server's network has to reach the API.
If history or changes are missing
- Guest single request results are not saved.
- A request you typed is not linked to a saved request just because the URL matches. Open and run the saved request.
- A quick request from Single request has no row on the board.
- The first completed response sets the contract baseline; a change report appears only after a later change.
- Performance findings need several comparable runs, so one slow call is not a false alarm.
- A paused monitor does not run. Check its state, last error, next run, plan and limits.
- A project that is not open to you at all says it is not open to you.
- The Executions list of a request may be filtered. "All runs" above the filters shows which saved view is on; pick "All runs" to see every run. Save the filters you use often as a view, or share it with your team.
Related
- /help/api-testing/send-to-localhost
- /help/api-testing/permissions-sharing
- /help/settings/plan-limits