Versions Compared


    • This line was added.
    • This line was removed.
    • Formatting was changed.
    Comment: DOCS-4477

    Appd tocbox

    On this page:

    Table of Contents

    Related pages:

    Synthetic jobs are configurable, scheduled tests consisting tests that mimic end-user actions in remote browsers in supported locations. Synthetic jobs consist of URL measurements or synthetic scripts. To create a job, see see Get Started with Browser Synthetic Monitoring.  

    Synthetic Job Support

    Browser Compatibility 

    • IE6/7/8/9/10/11/Edge
    • Chrome, including Mobile
    • Firefox, including Mobile 
    • Safari, including Mobile
    • Opera

    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. 

    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

    The Junior maturity

    level consists

    level consists of


    synthetic jobs that

    were just

    are created or updated within

    the last

    two hours.


     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



    SeniorThis 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 PriorityJob TypeLicense TypeJob 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 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.


    Max Queue SizeJob PriorityJob TypeJob Maturity
    Number of Synthetic Agents * 10 (Pro)High ScheduledSenior
    Number of Synthetic Agents * 10 * 0.5 (Trial)
    Number of Synthetic Agents * 10 * 0.25On-DemandN/A
    Number of Synthetic Agents * 10 * 0.5LowScheduledJunior


    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