Skip to main content

Limits

The limits Script Master applies to items, history and runs. They're the same in Jira and Confluence, except where a row names one product.

Items per site​

ItemLimitWhat to do when you reach it
Fragments100Delete fragments you no longer use, or combine small ones
Gadgets (Jira)100Delete gadgets you no longer use
Macros (Confluence)100Delete macros you no longer use
UI modifications (Jira)100Delete UI modifications you no longer use
Web triggers100Delete web triggers you no longer use, or handle several actions in one web trigger
Scheduled jobs5Combine jobs that run at the same time into one script

100 is the largest page that one Forge storage query returns, so Script Master can read a whole list in one request. When you reach a limit, creating another shows You've reached followed by the limit, for example You've reached 100 web triggers.

Fields​

FieldLimit
Title of a fragment, gadget, macro, web trigger or scheduled job128 characters
Description of a fragment, gadget, macro or scheduled job256 characters
Name of a UI modification255 characters
Schedule of a scheduled job128 characters
Code of one item, such as a fragment, web trigger, scripted field or post function230 KiB. Saving longer code shows The code is followed by its size, and The limit is 230 KiB. Move large libraries out of the code and load them instead
Note on a version200 characters
Maximum height (px) of a macro on a page (Confluence)100 to 10,000 pixels, or blank for no limit
Rules and settings of one UI modification, as stored in Jira50,000 characters, a Jira limit
Checks in one validator or condition rule (Jira)10
Message of a validator rule (Jira)300 characters

History​

WhatKept
Versions of an itemThe latest 50. The oldest is deleted when a new version is saved
Runs of a web trigger, scheduled job or post functionThe last 10
Successful runs of a web trigger or post functionAt most one every 5 minutes per item. Runs that fail or log an error are always kept
Last 7 days activityUp to 100 runs and 100 failures per item per day. Busier days show 100+
Failures of a fragment, gadget, macro or UI modificationAt most one recorded every 5 minutes per item, with a message of up to 300 characters

See Run history and Version history.

Output of one run​

WhatLimit
Console lines100 lines, each up to 2,048 characters, and 150,000 bytes in all. Lines past the limit are dropped, and a warning says how many
Return value kept in the historyThe first 2,048 characters
Error kept in the historyThe first 2,048 characters

Time​

WhatLimit
Test of a scheduled job24 seconds
A scheduled job's startScript Master checks for due jobs once an hour, so a job can start up to an hour after its time. Schedules are in UTC
A work item in the scripted field preview (Jira)22 seconds. In Jira, a field that takes longer than 25 seconds shows no value
Work items in one scripted field preview (Jira)50
A fragment, gadget or macro loading in the browser20 seconds. Content that hasn't loaded by then is recorded as a failure
Calls to web triggersAbout 10 calls in 20 seconds for all web triggers of a site. Calls over that can get 429 Too Many Requests
Values of one scripted field (Jira)Jira asks for values in batches. Over about 10 batches in 20 seconds for one field, the extra batches show no value
The Companion App status check10 seconds

Other​

WhatLimit
Code loaded from an external editor2 MB
Unsaved editor changes kept in your browser7 days