A signal fails to fire when the source isn't connected, the trigger conditions don't match, the signal is stale, or (for custom signals) the API payload is malformed. Check the signal's configuration and recent activity log.
Check the source and config
Signals → your signal → Activity. Confirm the source is connected and the trigger conditions (keywords, thresholds, account filters) actually match real-world events. Overly narrow conditions are the most common reason a signal looks "broken" when it's just never matching.
Custom signals via API
If you fire signals with POST /signals (see Core endpoints reference), a 422 validation_failed means a malformed payload — check the details array for the field at fault. A 401 means a bad key (see Authentication and API keys). Log the request_id so support can trace it.
Freshness and dedup
Signals decay and turgo dedupes repeats so the agent isn't triggered twice by the same event. If you expected a re-fire on an already-seen signal, that suppression is intentional.
Fixes
Reconnect the source, loosen conditions that are too strict, fix the API payload for custom signals, and confirm the signal is enabled and wired to an agent response (see Signal-triggered plays). Then trigger a test event and watch the activity log.
