On this page: Related pages:
On this page:
Synthetic Job Types
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.
Synthetic Job Locations
For URL measurements and synthetic script jobs, the Synthetic Agent is always run in the configured browser location. The synthetic script, however, is not run on the same machine or location as the configured browser for security reasons. See Synthetic Agent Locations for more details.
Synthetic Job Queue
When you create a 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 queue. On-demand jobs are placed in the same queue, but are not assigned a maturity level.
Maturity Level for Scheduled Jobs
Jobs are assigned a maturity level based on when they are created and added to the queue. The following table describes the two supported maturity levels.
|Junior||This maturity level consists of the synthetic jobs that were just created or updated within the last two hours. Once two hours have passed since the last update or creation of the job, the job will be promoted to Senior. The promotion from Junior to Senior is only performed when the required capacity has been allocated to avoid negatively affecting the current executing jobs.|
|Senior||This maturity level consists of scheduled jobs that have been created or updated more than two hours ago. The synthetic jobs with the maturity level of Senior have been allocated resources to be executed.|
Synthetic Job Execution
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 Browser Synthetic Monitoring license.
Job Execution Order
The following table 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 Type||Job Seniority|
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 will be added to the queue until the queue size decreases. 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 Size||Job Priority||Job Type||Job 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.5||Low||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 end.
|Error Message||Cause of Error||Error Code|
|Skipped; still waiting for a previous job execution||An 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.|
|Skipped while new capacity is being added||An 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.|
|Skipped while new capacity is being added||An attempt was made to queue a measurement request from a junior job beyond the maximum respective queue capacity.|
|Testing location is overloaded||An attempt was mad to queue a measurement request from a senior job beyond the maximum respective queue capacity.|