CloudShell Version: 8.3 GA

Help Version: 1.2

Api Guide
View / Download All Help Versions
Online Help

This help article applies to CloudShell 8.3. To see the latest, click here.

You are here: Job Scheduling > Running Automation Suites

Running Automation Suites

There are three types of automation suites that can be run: automation suite templates that can be run multiple times, customized versions of an automation suite template, and an ad hoc automation suite which you define on the fly and run once.

Note: Ad hoc automation suites are available for all user types while automation suite templates are only accessible to admins and to non-admin users that have permission to access those templates.

These are explained in detail in the following articles:

Note that the defined execution time of the suite is not necessarily the time at which the suite is executed. First, the suite enters the queue and waits for a matching execution server to become available and the requested sandbox (if defined) to become active.

In addition to the requested start time specified for the automation suite, there are three job settings that influence the actual execution start time:

  • Resource availability in the job's requested blueprint
  • Execution server availability
  • Job duration

    Note: The next en-queued job will not run if the current job's duration has not completed, even if its tests have completed their execution. The admin can use the QacAllowedTimeFrameDurationInMinutes key to search for available job slots to run the following jobs.

Related Topics