Review Marketplace apps with high database usage

This recommendation is shown when we’ve detected that one or more Marketplace apps are spending an unusually long time running database queries, which may be affecting performance and page load times.

Signals used

Details of how we detect this issue.

Conditions

The following conditions need to occur together:

• At least one of the key experiences, such as issue view, shows degraded page load times (RFU)

• The db.core.executionTime metric for a Marketplace app was degraded over the same time window when RFU degraded, compared to previous weeks

• The db.core.executionTime metric is degraded for fewer than 5 apps. This number makes it more likely that the issue is actually related to these apps and isn’t a broader system problem.

Filters

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

• For degraded experiences, we show the highest degradation from all occurrences.

• For identified apps, we list all apps that contributed to this issue. For each app, we show the percentage of all occurrences it caused.

Frequency chart

Similar to filters, the frequency chart shows occurrences of this issue over time. It can help you spot specific patterns, for example apps causing high database usage during a specific day of the week or time of the day.

Recommended action

Review and investigate identified apps

How to solve this issue will depend on a Marketplace app and what it does. Here are some actions you can take:

• Review the affected apps
  Check the list of apps reported in the recommendation. Confirm whether any of these apps have had recent changes, such as new automation rules, features, configuration updates, or version upgrades.

• Look for heavy or unusual usage patterns
  Identify whether specific projects, workflows, or custom features in those apps line up with the time window where performance degraded. Pay attention to very frequent operations, large data updates, or newly introduced reports and dashboards that may be driving extra load.

• Optimize or temporarily reduce load, or disable the app
  Where possible, simplify or reduce the frequency of rules, jobs, and reports driven by the identified apps. Avoid running large bulk operations during peak hours, and consider pausing non‑critical automations or features, or temporarily disabling the app, to see if performance improves.

• Contact the app vendor (if needed)
  If performance issues continue after you adjust configuration or usage, reach out to the app vendor. Share that you’re seeing high db.core.executionTime, the time window when RFU and database execution time degraded, and any recent configuration or usage changes so they can advise on optimizations or fixes.