View Categories

Automation Execution Delay

1 min read

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.

  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




    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.

    These reports are found under Automations > Related Settings

    Automation usage reports




What are your Feelings
Scroll to Top