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β
| Limit | Value | Applies to | At the limit |
|---|---|---|---|
| Items per run | 5,000 | Every tool that searches | The run uses the first 5,000 matches, and the report says so. Narrow the scope and run again for the rest. |
| Attachments per run | 1,000 | Delete old attachment versions | Lower because the tool reads each file's history before you confirm. |
| Pages in a page tree | 100, the picked page included | Delete attachments in bulk, Delete old attachment versions | The Page tree field says the tree is too large. Pick a page lower in the tree, or use Custom scope (CQL). |
| Parent pages followed | 500 | Add a label to parent pages | The tool stops following the chain. |
| Snippet length | 50,000 characters | Insert content into pages | The form doesn't accept a longer snippet. |
| Keep at least | 100 | Delete old attachment versions | The form doesn't accept a higher number. |
| Custom age | 100 | Both attachment tools | The form doesn't accept a higher number. |
| Pages copied | No limit set by Script Master | Clone a space | Confluence 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 happens | Result |
|---|---|
| One item fails | The run carries on. The summary lists up to 10 failures with the reason for each. |
| The search fails | The run stops before it changes anything. |
| A Clone Space copy fails after the space was created | The 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.
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:
- Insert content into pages skips pages that already have the snippet.
- The two label tools change nothing on a page that already has the label.
- Replace a label across content finishes items that got the new label but still have the old one.
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.
Relatedβ
- Tools: every tool and how a run works.
- Set who can use each tool: who sees each tool on the page.
- A tool run stopped partway through: what to do next.