---
title: Automation Execution Delay
description: "Issue: The tenant experienced a delay in automation execution. Root Cause: The tenant is hosted on a shared cluster with other tenants from the same client. A high volume of automation triggers from this other tenant caused the delay. Steps to debug: ..."
url: "https://supportb.kinsta.cloud/docs/automation-execution-delay/"
updated: "2025-08-17"
category: "FAQ: Automations"
---

# Automation Execution Delay

**Issue:**
The tenant experienced a delay in automation execution.

** Root Cause:**
 The tenant is hosted on a shared cluster with other tenants from the same client. A high volume of automation triggers from this other tenant caused the delay.

**Steps to debug:**

1. **Check Tenant Cluster Type:**
    Confirm if the tenant is on a dedicated or shared cluster via the provided link. The Cluster ID is available in the Lead root.
    Link: [https://reports-sg.leadsquared.com/CommonServices/AutomationUsageQuery.aspx?ClusterId=2037](https://reports-sg.leadsquared.com/CommonServices/AutomationUsageQuery.aspx?ClusterId=2037)
2. **Monitor Automation Execution:**Use Grafana dashboards to check for automation execution delays.
   Link: [https://grafanamonitorv2.leadsquared.co/d/gqs8mcayy/pulsar-topic?orgId=1&var-DS_PROMETHEUS=Automation-Unified-Observability-MUM&var-cluster=pulsar-cluster-1](https://grafanamonitorv2.leadsquared.co/d/gqs8mcayy/pulsar-topic?orgId=1&var-DS_PROMETHEUS=Automation-Unified-Observability-MUM&var-cluster=pulsar-cluster-1)

   ![](https://desk.zoho.in/galleryDocuments/edbsn5ca1358b5f116347b6b9c1b223d6868a878c3c540a0c51d027fda42a9d88b12b8b6bec7028339c6266864f5a86f5c51e256cad3775d688488d906fe5ede50b4a)

   ![](https://desk.zoho.in/galleryDocuments/edbsn5ca1358b5f116347b6b9c1b223d6868ab06e854c7d1eca84b8f5e5e09b4f683e14ff1c28d87f6d86951a1217be1c32c52f9c72c9d3b7c96297ac8753d1233474)
   **NumberOfConsumersConnected**refers to the number of consumers actively used to process automation messages.
   In this case, the value auto-scaled from 2 to 6 in response to the message processing delay, allowing the system to handle the increased load more efficiently.
3. ** Analyse Surge in Automation Messages:**If a surge is observed in Step 2 and the customer requests logs, note that backend message logs are unavailable. Use Automation Usage reports instead, which the Billing team can enable.
   ![](https://desk.zoho.in/galleryDocuments/edbsn5ca1358b5f116347b6b9c1b223d6868ad807ae3eadd636d0fa31dca051d682ac174beac7e06fb38ba493b18fe09ecf9a569d20bf9f04f188558e2d758a780fb0)
   These reports are found under **Automations > Related Settings
   ![](https://desk.zoho.in/galleryDocuments/edbsn5ca1358b5f116347b6b9c1b223d6868ab13d15c39c90716227e15badd28ddfb0d8bed9d457a8afc34de7a8b624bdbf871aec0f60b195a36ebbfc42d454af8f71)**Automation usage reports**![](https://desk.zoho.in/galleryDocuments/edbsn5ca1358b5f116347b6b9c1b223d6868a88b5c3b79179aff54c87c7e87f46c488b94cb3520b1581a9c5a808d7e67a762bc512c20777357bf9a3cf6dab1d302e74)**