Trigger Logs allow you to review communications that have been sent, preview messages before sending, resend communications when necessary, and diagnose delivery issues.
Monitoring trigger activity is an important part of maintaining reliable automated communication workflows. The logs help confirm that triggers are behaving as expected and provide insight when communications fail or appear to send incorrectly.
What Trigger Logs show
Trigger Logs provide visibility into communications generated by a trigger, including whether the communication was sent successfully or if an issue occurred during processing.
- Communication status
- Recipient information
- Message preview
- Delivery feedback and errors
Reviewing logs is the fastest way to confirm whether a trigger ran and how the resulting communication was processed.
Preview or send communications
In addition to reviewing results, Trigger Logs allow administrators to preview and manually send communications generated by triggers.
Manual sending is useful when:
- Testing a new trigger that is configured for manual sending
- Resending a communication that previously failed
- Reviewing the final message content before automation is enabled
Printing communications
In some situations, postal communication may be required instead of digital delivery. Administrators can print communications directly from the Trigger Logs.
To print a communication:
- Open the relevant communication entry in the Trigger Log.
- Select the print icon.
- Follow your computer's printing instructions.
Common trigger errors
When a communication cannot be sent successfully, the Trigger Log will display an error message explaining the issue. Reviewing these messages helps identify configuration or data problems.
Missing “To” address
Every trigger email must include at least one valid recipient in the To Address field. If no valid address exists, the communication will not be sent and the trigger status may appear as Invalid.
This situation commonly occurs when the intended recipient does not have a valid email address recorded in their contact record.
Even if a communication includes addresses in the CC field, at least one valid address must exist in the To field for the communication to send.
SMS delivery errors
SMS delivery failures may occur due to country-specific messaging rules or carrier restrictions.
For example, some countries restrict certain sender name formats or require specific SMS routing configurations. These rules vary by destination and are controlled by the SMS provider.
Administrate uses Twilio as its SMS delivery provider.
If SMS errors persist after confirming country requirements, contact Administrate support with the details from the Trigger Log entry.
Using logs to diagnose trigger behavior
If a trigger does not behave as expected, reviewing the Trigger Log can help determine whether the issue is related to trigger configuration, scheduling, or recipient data.
When diagnosing issues, review:
- Whether the trigger executed
- Whether the communication was generated
- Whether the message was successfully delivered
- Any delivery errors or warnings reported
This information helps determine whether adjustments are required in the trigger configuration, recipient records, or communication template.