This article outlines potential reasons why a trigger is not sending messages to any subscribers, along with actionable troubleshooting steps.

Common Reasons and Troubleshooting

1. Throttle is Set to 0

• If the throttle rate of the activity is set to 0, the trigger will be paused and will therefore not be sent.
• Check: Review the activity log and throttle rate.

  Note: If the throttle is set to 0, before changing it, please check to see if there are messages in the queue. If there are, please reach out to support to clear this before you change the throttle and resume deployment.

2. Overlapping Activities Causing Delay

• Multiple activities being triggered at the same time can lead to queuing or delays in processing.
• Check: Review the activity logs and system queue for congestion or timing overlaps.

3. Incomplete or Incorrect Activity Configuration

• Required fields within the activity may be missing or invalid, causing the system to skip or fail the trigger.
• Check: Make sure all necessary activity fields are filled in correctly and that the activity check passes its internal validation checks.

4. Incorrect or Invalid Target Expression

• An invalid or overly strict target expression can result in no matching subscribers.
• Check: Verify that the target expression is syntactically correct and correctly identifies the intended subscribers.

Recommended Checks Summary

Area	What to Check
Activity Throttle	Is the activity throttle set to 0?
Activity Timing	Are other overlapping activities causing queue delays?
Activity Configuration	Is the activity check passing?
Target Expression	Is it valid and selecting the correct audience?
Subscriber Matching	Do subscribers meet the criteria set by the trigger?
Subscriber Status	Are the intended recipients active and subscribed?
Template/Channel Setup	Are all templates valid and delivery channels properly set?

If you have any further issues with your triggers, please contact Taguchi Support for further assistance.

---