Limits and troubleshooting
This page lists the numbers that apply to TuneCraft, the messages you may see and what to do about each.
On this page
Points budgets
Jira gives an app a pool of API points, shared by every site that has the app. TuneCraft stays within two budgets for each site, so it never starves your own users or other sites.
| Budget | Per hour and site | What uses it |
|---|---|---|
| Background checks | 600 points | The tools' readings of Jira by themselves |
| Work a person starts | 2,400 points | A reading a page starts, a label change, a filter preview, a Spaces versions reading |
Jira counts 1 point a request, 1 an object it returns, 2 for users, groups, roles and permissions, and only the request for a write. App cost shows what TuneCraft spent, measured by its own meter, which can differ from Jira's count.
When a budget is spent, a long reading stops and says when it carries on. It resumes where it stopped, and it needs the page open if a person started it. A reading never starts again from the beginning.
Numbers that apply
| What | Limit |
|---|---|
| Export file size | 50 MB for each file |
| Corrected flow file | 5 MB, the most Jira imports at once |
| Scans kept | The last 24 |
| Dependency links kept | 50,000 in all, 50 for each flow |
| People in a notice | 10 |
| People search | 2 characters of a name before it asks Jira |
| Label copies read | 10,000 labels |
| Alerts, history, usage | 400 days |
| Undo of a filter, dashboard or label change | 30 days |
| Database | 1 GiB in production |
| Trial changes in Filters | 10 objects |
| Trial changes in Labels | 10 changes, 1,000 work items each |
Common messages
| Message | What to do |
|---|---|
| "This site has no active TuneCraft licence." | A Jira admin starts a trial or buys a licence in Apps > Manage apps. See Licence and trial. |
| "You don't have access to TuneCraft." | A Jira admin gives your group access in App access. |
| "You can read TuneCraft's reports but not change anything." | A Jira admin gives your group the Manage level. |
| "Only Jira admins can use this tool." | Ask a Jira admin. The tools other than Automation are for Jira admins. |
| "Jira could not confirm what you may do in TuneCraft." | Try again in a minute. TuneCraft denies when it cannot check. |
| "Jira is limiting requests from this app. Try again in N minutes." | Wait. Jira asked the app to pause. |
| "TuneCraft has spent this hour's Jira points for work people start on this site." | Wait for the time shown, with the page open. |
| "TuneCraft is busy. Please try again in a minute." and "TuneCraft is updating." | Wait a minute and try again. |
| "This tool's background checks are off." | A Jira admin turns them on in the tool's settings. |
| "This scan is no longer open." or "Some flows of this scan did not arrive." | Scan the export again. |
| "TuneCraft is still reading this scan." | Try again in a moment. |
| "N is not a JSON file" or "holds no automation flows" | Export the flows again from Jira's Global automation and choose that file unchanged. |
| "A CSV file is not an automation audit log as Jira exports it." | Export the audit log again from the Audit log tab of Jira's automation page and choose it unchanged. |
| "Reading Jira stopped: Jira's pool of points for TuneCraft is nearly spent." | It carries on after the time shown. |
| "The scan is saved, but its flows were not kept: TuneCraft's database is nearly full." | Open Database size, and delete old scans on History. The next scan tries again. |
| "Jira did not confirm the work items: some may have been created." | Check the project before you send the notices again. |
Things to check when something looks wrong
- A tool shows nothing. Its background checks may be off or may not have finished their first reading. The page says "No ... read yet". Turn them on, and keep the page open if it says reading carries on.
- A tool's reading waits. If no Jira admin opened the tool in 60 days, its checks wait. Opening the tool starts them again.
- Flows are missing from "used by". The last scan may be old (more than 7 days), may not hold every flow, or may have kept no record of what flows use. Scan again. TuneCraft never says "no flow uses it" when it cannot know.
- Step numbers look different from Jira's Usage tab. TuneCraft's numbers are estimates unless the flow has measured counts. Add the audit log to a scan, or type measured steps on Assumptions.
- The corrected flow does not import. The file must be under 5 MB. Choose the export again so the real values can be put back.
- A count of work items looks low. Jira counts only the work items TuneCraft can browse, and a count can be up to 7 days old.
If a problem remains, collect a Support bundle (see Administration) and send it to Plugincraft through the contact page. The bundle holds no flows, names, account ids or site names.
Questions about the app? Write to info@plugincraft.ca.