Review Marketplace apps with long-waiting threads

This recommendation appears when we detect one or more Marketplace app threads that have been waiting for a resource for an unusually long time, say 40 seconds or longer. This can degrade page load performance.

Threads in a WAITING state are paused. They are stuck waiting for a signal from another part of the application before they can continue. While waiting, they still occupy a slot in the thread pool. Common causes include waiting for another thread to finish a task, waiting for a shared resource to become available, or waiting for a condition that has not yet been met.

When many threads are stuck at this state, it can cause severe performance bottlenecks. We display the number of waiting threads in the recommendation to help you better understand memory usage and prevent application unresponsiveness.

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 WAITING 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-waiting threads section, we list Marketplace apps that have long-waiting threads. For each app, we show the maximum number of concurrent waiting threads.

Frequency

Similar to filters, the Frequency section shows occurrences of this issue over time. It can help you spot patterns, for example, long-waiting threads that occur when a specific external service is slow, during high-traffic periods, or after a configuration change that increased the number of outbound calls.

Recommended actions

We recommend that you review and investigate the identified apps. The process for solving 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-waiting thread spikes

Identify whether long-waiting threads coincide with specific user actions, scheduled tasks, synchronization jobs, external API calls, or traffic peaks. This can help determine whether the app is consistently slow to receive responses or only under certain conditions.

Review the connection pool and timeout configuration

If the Marketplace app exhausts its HTTP or database connection pool, the threads will wait for a connection to become available. Consider increasing the pool size if appropriate, or reducing the number of concurrent outbound calls. Additionally, review the timeout settings to ensure threads don't wait indefinitely for unresponsive external resources.

If issues persist, contact the app vendor

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