Review Marketplace apps with long-running threads

This recommendation appears when we detect one or more Marketplace app threads actively executing for an unusually long time, say 40 seconds or longer, coinciding with degraded page load performance.

Threads in the RUNNING state hold resources, such as (but not limited to) database connections or locks, for extended periods. This can starve other threads of the resources they need, which can contribute to slower request handling and degrade overall instance responsiveness.

An excess of such tasks can overload the processor. In order to give you a better understanding of the current system health and resource consumption, we display the number of running threads in the recommendation

Signals used

For us to detect this issue, the following conditions need to occur together:

  • At least one of the key experiences shows degraded ready-for-user (RFU) page load times.

  • Ten or more threads are identified in a RUNNING state for more than 40 seconds in a Marketplace app.

Filters

When the issue occurs multiple times, we group their signals under different filters, for example, Last 24 hours or Last 7 days. In this case:

  • In the Degraded experiences section of the recommendation, we show the highest degradation from all occurrences.

  • In the Apps with long-running threads section, we list Marketplace apps with long-running threads. For each app, we show the maximum number of concurrent long-running threads.

Frequency

Similar to filters, the Frequency section shows occurrences of this issue over time. It can help you spot patterns, for example, long-running threads that occur during scheduled jobs, heavy indexing operations, peak usage hours, or after specific app configuration changes.

We recommend that you review and investigate the identified apps. The process to solve this issue will depend on the Marketplace app and what it does. Here are some actions you can take:

Review the affected Marketplace apps and their operation type

Check the Marketplace apps listed in the recommendation and note the operation type. This can help you understand the actions performed by the affected apps. To view a full breakdown of every affected app, select Download CSV. The CSV file provides detailed data that supports this recommendation, including different operation types. More about operation types

Look for patterns that align with long-running thread spikes

Identify whether long-running threads coincide with specific user actions, scheduled tasks, synchronization jobs, indexing, reporting, automation rules, or traffic peaks. This can help narrow down whether the Marketplace app is causing constant slow execution or only under certain conditions.

Reduce or optimize slow app activity

Where possible, tune the Marketplace app configuration to reduce execution time. Try lowering job frequency, optimizing queries, disabling non-essential background tasks, or moving heavy operations away from peak usage periods. Additionally, if possible, you can temporarily disable the Marketplace app to check if long-running thread counts improve.

If issues persist, contact the app vendor

If performance issues continue, contact the app vendor. Share that you're seeing long-running threads. Mention the affected time window, the operation type, the median and maximum thread duration, and any recent configuration or usage changes so they can help identify opportunities to optimize or fix the issue.

Still need help?

The Atlassian Community is here for you.