Skip to main content

Tools limits and behavior

This page lists the limits of a Tools run and what a run does when it reaches one, retries a request or stops partway.

Applies to: Script Master for Jira and Script Master for Confluence Β· Cloud

Limits​

LimitValueApplies toAt the limit
Items per run5,000Every tool that searchesThe run uses the first 5,000 matches, and the report says so. Narrow the scope and run again for the rest.
Attachments per run1,000Delete old attachment versionsLower because the tool reads each file's history before you confirm.
Pages in a page tree100, the picked page includedDelete attachments in bulk, Delete old attachment versionsThe Page tree field says the tree is too large. Pick a page lower in the tree, or use Custom scope (CQL).
Parent pages followed500Add a label to parent pagesThe tool stops following the chain.
Snippet length50,000 charactersInsert content into pagesThe form doesn't accept a longer snippet.
Keep at least100Delete old attachment versionsThe form doesn't accept a higher number.
Custom age100Both attachment toolsThe form doesn't accept a higher number.
Pages copiedNo limit set by Script MasterClone a spaceConfluence copies the tree. Above 500 pages, the check warns that the copy takes a while.

Retries and failures​

Atlassian limits how fast an app can call its APIs. When Jira or Confluence answers with HTTP 429 (too many requests), the tool waits and retries. It tries up to 3 more times, after 1, 2 and 3 seconds. It doesn't retry other errors.

What happensResult
One item failsThe run carries on. The summary lists up to 10 failures with the reason for each.
The search failsThe run stops before it changes anything.
A Clone Space copy fails after the space was createdThe screen names the new space and offers to delete it.

Where a run happens​

Every tool runs in your browser, as you, and works through the items one at a time. A tool changes only what you could change by hand. No Forge time limit cuts a long run short, but the tab has to stay open.

warning

If you close or reload the tab during a run, the run stops. Items it already changed keep the change, items it didn't reach stay as they were, and you get no summary. See A tool run stopped partway through.

No tool can resume a stopped run. Some are safe to run again on the same scope:

What isn't recorded​

Tools keep no run log. The summary on screen is the only record of what a run changed and what failed, so copy it before you leave the page.

Jira and Confluence keep their own trail of some changes. Confluence page history shows the versions Insert content into pages makes. Jira work item history shows the field edits of the Jira tools.