Resources »

Tips »

Identify problematic automations or behaviors

You can use a data query to identify which automations or behaviors have run in the past month and how many times. If an automation runs too often, you can optimize it with better disabled@bool: conditions in the automation event.

You can add these queries to a chart or run then in the data query tester found in Setup » Developers » Data Query Tester:

type:metrics.timeseries
series.automations:(
  metric:cerb.automation.invocations
  by:[automation_id]
)
series.behaviors:(
  metric:cerb.behavior.invocations
  by:[behavior_id]
)
range:"-1 month"
period:year
format:dictionaries

You can find the slowest automations and behaviors (in milliseconds) with this query:

type:metrics.timeseries
series.automations:(
  metric:cerb.automation.invocations
  by:[automation_id]
)
series.behaviors:(
  metric:cerb.behavior.invocations
  by:[behavior_id]
)
range:"-1 month"
period:year
format:dictionaries