Rerun Test Plan

the endpoint allows the user to rerun specific scenarios of a test plan endpoint information url {gateway url}/queue/rerun method post authentication required ( bearer token ) request headers header required description authorization yes bearer token used to authenticate the request format bearer \<your access token> content type yes must be application/json x company id yes company context for the request the authenticated user must have access to this company request body { "planid" 704, "userid" 1, "frameworktype" "selenium4", "forcerun" false, "scenarioenvironmentpairs" \[ { "scenarioid" 4267, "environmentid" 2001 } ] } request body parameters parameter type required description planid long yes the unique id of the test plan to rerun userid long yes the unique id of the user who triggers the rerun frameworktype string yes test framework type allowed values selenium , selenium4 , appium , appium2 , service , playwright forcerun boolean no indicates whether the rerun should be forced default false scenarioenvironmentpairs array yes list of scenario/environment pairs to rerun must contain at least one item scenarioenvironmentpairs\[] scenarioid long yes the unique id of the scenario to rerun scenarioenvironmentpairs\[] environmentid long conditional required for selenium , selenium4 , appium , and appium2 optional for service and playwright response this response indicates that the rerun request was accepted successfully no additional response data is returned {} error response format { "instance" "/queue/rerun", "status" 404, "title" "not found", "type" "https //errors testinium com/exception", "timestamp" "2026 08 18t12 08 41 165927056z", "errortype" "exception", "errors" { "code" 10002, "message" "user with id 1666666 not found!" } error response fields parameter type description instance string the request path where the error occurred status integer http status code title string short http error title type string error type reference url timestamp string error timestamp in utc errortype string internal error category, such as exception , validation , or confirmation errors object or array application level error details validation errors may be returned as an array errors code integer application specific error code errors message string human readable error message this may be localized based on request language errors field string field related to the error this field may not always be returned error codes http code error message description 400 bad request request body is invalid, malformed, or contains validation errors 401 unauthorized bearer token is missing, invalid, or expired 403 forbidden the authenticated user does not have permission to access the resource 404 not found a referenced resource, such as plan or user, could not be found 409 conflict the plan is already running 410 gone a referenced entity is disabled or deleted 422 unprocessable entity the request is syntactically valid but cannot be processed due to business rules 500 internal server error an unexpected server side error occurred 503 service unavailable gateway or an upstream service is unavailable application error codes code http status source description 10000 404 queue plan not found 10002 404 queue user not found 10013 422 queue no scenarios are associated with this plan 10001 404 queue no environment is associated with this plan 10004 410 queue entity is not enabled 10005 410 queue entity is deleted 10012 409 queue plan is already running 10008 422 queue environment is not registered returned with errortype confirmation 10007 422 queue required app file is missing for the project 10014 422 queue no build is assigned to the plan 20005 400 common request body validation error, such as missing planid , userid , frameworktype , or scenarioenvironmentpairs 10001 401 gateway authentication is required 10002 401 gateway token is invalid or malformed 10003 403 gateway user does not have permission to access the resource 10004 400 gateway required x company id header is missing or malformed 10008 503 gateway routed service is unreachable note application error codes may overlap between services use the source , http status, and response message together when interpreting errors example request curl location '{{gateway url}}/queue/rerun' \ header 'content type application/json' \ header 'authorization bearer \<your access token>' \ header 'x company id \<company id>' \ data '{ "planid" \<plan id>, "userid" \<user id>, "frameworktype" "selenium4", "forcerun" false, "scenarioenvironmentpairs" \[ { "scenarioid" \<scenario id>, "environmentid" \<environment id> } ] }'