Learn why your Cotonity agent may fail to fire on schedule or in response to events, and how to diagnose and resolve the most common trigger issues.
Why triggers fail
An agent that appears inactive is almost always caused by one of a handful of configuration issues rather than a platform outage. The most frequent culprits are: the agent is paused or disabled, the trigger condition evaluates to false because of a mismatched filter value, the connected data source has not yet emitted the expected event, or the agent's activation schedule has expired. Before diving into logs, verify the agent's status badge in the Agents dashboard shows 'Active' and that the next scheduled run time appears in the detail panel. A greyed-out badge always means the agent needs to be manually re-enabled.
Checking trigger conditions and filters
Open the agent editor and navigate to the Trigger tab. Review every filter rule carefully — a common mistake is using an exact-match condition on a property that contains leading or trailing whitespace, or comparing a number to a string. Cotonity evaluates filter rules top-to-bottom and stops at the first failing condition, so a single incorrect rule can silently block all executions. Use the 'Test trigger' button to send a sample payload through the filter chain and inspect which rule passes or fails. The test panel shows the exact evaluated value for each field, making it straightforward to spot type mismatches.
Event source connectivity
If the trigger type is 'webhook' or 'integration event', the issue may lie with the upstream system rather than Cotonity. Navigate to Settings > Connections and confirm the connected app shows a green 'Connected' indicator. For webhook triggers, copy the endpoint URL from the trigger configuration and confirm the sending system is posting to that exact URL with the correct HTTP method (POST is required). Cotonity logs all incoming webhook requests — including rejected ones — under Agent Activity > Incoming Events, which lets you verify whether payloads are arriving at all.
Quick checklist
Work through this checklist before opening a support ticket: (1) Confirm the agent status is Active. (2) Verify the trigger schedule or event source is configured correctly. (3) Run a test trigger and check which condition fails. (4) Inspect the connection status for any linked integration. (5) Review the Activity log for the past 24 hours to see if any runs were attempted but silently discarded due to filter mismatches. Most trigger issues are resolved within the first two steps of this checklist, so it is worth completing the full list before escalating.