How to determine why a scheduled test did not execute when there is no report or error seen

book

Article ID: 220364

calendar_today

Updated On:

Products

BlazeMeter

Issue/Introduction

A load test was scheduled to start this past Saturday (7/24) at 7am EST (11am UTC).

There are no indications that this test ever executed when scheduled.   There is no indication on the test history page nor is there any sort of failure report available indicating why the test did not execute.

What is the best way to determine why a scheduled test did not execute at the scheduled time.

Environment

Release : SAAS

Component : BLAZEMETER PERFORMANCE TESTING

Resolution

Determine the scheduleId of a test by executing the List Schedules API for a specific test.

The actual API call for the list of scheduleId's available for a test would look similar to the following:

curl -X GET --header 'Accept: application/json' \
  'https://a.blazemeter.com/api/v4/schedules?limit=100&projectId=<projectId>&workspaceId=<workspaceId>&accountId=<accountId>' \
   --user '<api_key_id:api_key_secret>'


The schedule history can be found by executing the List Schedule History API for scheduleId associated with the problematic test.

The actual API call for this schedule would look similar to the following:

curl -X GET --header 'Accept: application/json' 'https://a.blazemeter.com/api/v4/schedules/history?limit=10&scheduleId=<scheduleId>' \
  --user '<api_key_id:api_key_secret>'


A sample output of this command indicating why the test did not run at the scheduled time would be as follows:

{
  "limit": 10,
  "skip": 0,
  "total": 3,
  "hidden": 0,
  "api_version": 4,
  "error": null,
  "result": [
    {
      "id": "<internalTestId>",
      "runAt": 1627124405,
      "success": false,
      "reason": "Not enough available resources",
      "scheduleId": "<scheduleId>",
      "scheduleType": "testRun",
      "scheduleCronExpression": "0 11 * * 6",
      "created": 1627124402,
      "updated": 1627124405
    }
  ]
}