Limitations
- Pio
Our importer apps transfer large amounts of data from source systems and import them into JSM Assets. At this point, our apps have dependencies on 3 main external systems.
1- Source
Each source system provides different API endpoints with various performances. Sometimes, they respond slower than usual.
Some facts:
Microsoft Graph does not respond at the same speed for each of our customer's environments.
Microsoft Graph’s performance changes in the day. Especially with the hourly imports, we see that the data transfer takes longer in some hours than others.
Impact:
In case the imports take longer than the Forge Time limit, the import may be interrupted.
Solution:
Check your import logs and validate that they are running successfully. In case you see that they are not successful, follow the steps defined on the Operational Checks page.
2- Forge
Our applications run on Atlassian’s Forge Platform which allows us to deliver seamless user experience.
Some facts:
Forge also comes with platform limits. The most crucial limit for our applications is the invocation runtime limit. The limit defines the total runtime permitted before the app is stopped.
Currently, it is set to 25 seconds for all platform vendors. In summary, in case the data collection, filtering, formatting, and importing are not completed in 25 seconds Forge stops the application and displays an error message on your screen.
If the import process is a scheduled one, then Forge does not write any notification in the logs. You can only see that the import didn’t log a success message after the start message.
You may find the details of Forge Platform quotas and limits on the following page:
Impact:
Your imports can be interrupted by Forge.
Solution:
Decrease the number of data sets if they are not used.
Go to your Import tab. Check which data sets are enabled. In case you don’t need some of them, disable them and run an import. This way, you will decrease the number of API calls to your source and the import will run faster.
Filter the records from your source. (Only available for Azure AD Importer for JSM Assets)
Go to your Source tab. Find the Filter field. Follow the guidance on the Filter page.
If you are just testing the app, set a limit and perform your tests
Go to your Admin tab and set the max record to a low number.
Tip: Do not transfer data to your JSM environment if you will not use them. Every dataset should be helping JSM workflows run better and providing relevant, actionable information to the Agent who is working on the tickets/Issues.
3- Destination
JSM Assets allows our apps to import data in a programmatic way. JSM Assets, run separately from JSM and Jira Platform and thus has its own APIs.
Some facts:
JSM Assets feature has an agile development cycle and is updated frequently in an automated way. Mostly at night.
Our customers set scheduled imports hourly or daily in our apps. And most of the scheduled imports are running at night.
JSM Assets may be unavailable during the version upgrades. We get error messages in such cases.
Impact:
Your imports may fail.
Solution:
Check your import logs and validate that they are running successfully. In case you see that they are not successful, follow the steps defined on the page.