Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: DOCS-4650
Appd tocbox
Width300px

On this page:

Table of Contents
maxLevel2

Related pages:

Synthetic jobs can are configurable, scheduled tests that mimic end-user actions in remote browsers in supported locations. Synthetic jobs consist of URL measurements or synthetic scripts. You can run jobs at a specified frequency or request to run a job onceTo create a job, see Get Started with Browser Synthetic Monitoring.  

Synthetic Job

...

Synthetic jobs have two types: Scheduled and On-Demand. Those jobs that you configure to run at a specified frequency are called "Scheduled" jobs. You can make a request to run a job only once: this is known as an "On-Demand" job. Scheduled jobs generate synthetic sessions, whereas, On-Demand jobs generate synthetic snapshots.

You create "Scheduled" jobs through the Jobs page. To create "On-Demand" jobs, you use the On-Demand page or generate a synthetic snapshot from the Browser Snapshot Details dialog. 

Support

Browser Compatibility 

  • IE 10, 11
  • Chrome 64
  • Firefox 66 

Python Libraries

Synthetic Job Locations

For URL measurements and synthetic script jobs, the  the Synthetic Agent is always run in executed in isolation within a Docker container. This location is then mapped to the configured browser location. The synthetic script, however, is not  is run on the same a different machine or location as from the configured browser for browser for security reasons. See Synthetic Agent Locations for more details.

Synthetic Job Queue

When you create a synthetic job, it is added to a queue based on the creation timestamp. Scheduled jobs are assigned a maturity level that influences when they will be executed in the the synthetic job queue. On-demand jobs are placed in the same queue, but are not  assigned a maturity level. 

Anchor
maturity-level
maturity-level
Maturity Level for Scheduled Jobs

Jobs Scheduled jobs are assigned a maturity level based on when they are created creation time and added to the synthetic job queue. The following table below describes the two supported maturity levels.

Maturity LevelDescription
Junior
This

The Junior maturity

level consists

level consists of

the

synthetic jobs that

were just

are created or updated within

the last

two hours.

Once

 Once two hours have passed since the last update or creation of the job, the Junior job

will be

maturity level is promoted to Senior maturity level. The promotion from Junior to Senior maturity is only performed

when the required

only if enough capacity has been allocated

to avoid

. This avoids negatively affecting

the current

jobs which are currently executing

jobs

.

Senior
This
The Senior maturity level consists of
scheduled
synthetic jobs that have been created or updated more than two hours ago.
The synthetic
Synthetic jobs with
the
Senior maturity level
of Senior
have
been
ample allocated resources to be executed.

Synthetic Job Execution 

The synthetic job scheduler executes jobs according to the following cron-based expression:

<second> <minute> <hour> <day-of-month> <month> <day-of-week> <year>

When you schedule a job, you choose how frequently the job runs. It is recommended you choose a larger unit of time (hours or days) that can evenly divide into the smaller unit of time (minutes or hours). For example, if a job is scheduled to run every 15 minutes, the job runs four times within the hour. This results in the job consistently repeating every hour without interruption to the schedule.

However, if you schedule a job such that a larger unit of time that does not divide evenly into the smaller unit of time, such as running every 50 minutes, then the job does not run at consistent times. For example, if the first job starts at 7:03, then the job will run at 7:53, 8:03, 8:53, and so on, resulting in a disruption to the schedule.


Job Execution Order

The execution order of synthetic jobs depends on the job priority and the job creation time. The Synthetic Server job marks the priority of a job based on several factors: the job type, the job maturity, and your your Browser Synthetic Monitoring license. 

Job Execution Order

The following table  The table below shows the job priority based on the job type, license type, and job seniority. The actual job execution order depends on the the job priority and the job creation timestamp. 

Job Priority
Job Type
License TypeJob Seniority
High
Scheduled
ProSenior
Scheduled
TrialSenior
On-Demand
Pro
N/A
On-Demand
Junior
TrialN/A
On-DemandLiteN/ALowScheduledTrialJuniorScheduledProJunior

 


Synthetic Job Throttling

Synthetic jobs are only executed if they are in the job queue. If the max job queue size has been reached, however, no additional synthetic jobs synthetic jobs will be added to the queue until the queue size decreases. The  The max queue size is defined by the priority, license, type, and maturity level.

The following table shows how the maximum queue size is calculated:

Max Queue SizeJob PriorityJob
TypeJob
Maturity
Number of Synthetic Agents * 10 (Pro)High 
Scheduled
Senior
Number of Synthetic Agents * 10 * 0.5 (Trial)
Number of Synthetic Agents * 10 * 0.25
On-Demand
N/A
Number of Synthetic Agents * 10 * 0.5Low
Scheduled
Junior

 


Job Execution Errors

Customer is seeing different error messages with synthetic jobs and will like to understand their meaning and get more information to help with checking the issue at their endThe following table provides job execution error messages, the cause of the error, and the associated error code

Error MessageCause of ErrorError Code
Skipped; still waiting for a previous job executionAn attempt was made to queue a high-priority measurement request from a scheduled job before the previous measurement request from the same job, and location-browser combination has been processed.TARDY
Skipped while new capacity is being addedAn attempt was made to queue a low-priority measurement request from a scheduled job before the previous measurement request from the same job, and location-browser combination has been processed.TARDY_ONBOARDING
Skipped while new capacity is being addedAn attempt was made to queue a measurement request from a junior job beyond the maximum respective queue capacity.ONBOARDING
Testing location is overloadedAn attempt was
mad
made to
queue a
request measurement
request
from a senior job beyond the maximum respective queue capacity.THROTTLED