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

Steps

  1. Check that you are signed in, and in the workspace the project belongs to.
  2. Open Settings, "Plan & usage": does your plan include the feature, and is there capacity left?
  3. 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.
  4. 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.
  5. 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

Related