Add a deployment and trigger an additional round of testing for one of the sites in your team. A note is also automatically added to your charts.
Depending on the number of URLs you have it can take a few min to complete a round of tests across your site so we don't recommend making this a dependency for deployments. Rather you should trigger a post deployment request to the API to trigger a round of testing once your release is live.
Common reasons of getting 403 HTTP error status when submitting a new deploy:
- a deploy is in progress - only one deploy at a time is allowed on a specific site_id or url_id. You must wait for it to complete before kicking off another deploy.
- checks per month budget exceeded for the team - please increase checks budget for your account.
- some tests failed to be added - try later or contact the support team.
Error codes
HTTP code | Error | Reason |
|---|---|---|
400 |
| Please provide |
403 |
| Not enough checks to add a deploy. Increase your checks budget or contact support. |
403 |
| Deploy is in progress. Please try later. |
403 |
| No URLs found to test, please make sure you have at least one active site. |
404 |
| Provided team ID, site ID or URL ID is not found. |
500 |
| Server error, please contact support. |
503 |
| Server maintenance is in progress, please try later. |
Please also see the list of generic API error codes.