Overview
This article explains how to investigate delayed or skipped email transmissions for workflows that use the Graph App connector in Reindeer.
Common Symptoms
- Workflow runs start later than expected after an email is received.
- Expected email events do not create or update a case.
- Retries appear in the run history before the workflow continues.
Likely Causes
Graph App transmission delays usually come from one of a few operational causes:
- Transient upstream API errors that trigger automatic retries.
- Mailbox, event, or replication lag before Reindeer receives the relevant email event.
- Connector permission, mailbox rule, or configuration changes that affect event delivery.
- Payload or message attributes that do not match the workflow trigger conditions.
Impact on Workflows
Delayed or skipped email transmissions can affect workflows that depend on timely email processing, including payment approvals, quote handling, and exception routing. The main operational risk is inconsistent execution timing or a missing workflow run for an expected message.
Troubleshooting Steps
- Collect the affected case IDs, mailbox, message timestamps, and message identifiers when available.
- Confirm the connector configuration, mailbox permissions, and trigger rules are still valid.
- Review the run history and audit trail for retries, connector errors, or skipped trigger conditions.
- Check whether the message arrived later through retry or replication delay before treating it as lost.
- If the issue recurs, send the case IDs and timing details to support@reindeer.ai.
Monitoring and Support
Reindeer monitors Graph App transmission performance for stability and latency. For recurring failures, include affected case IDs, message timestamps, and connector details when contacting support@reindeer.ai.
Related Articles
- Managing and Troubleshooting Workflow Exceptions Detected by Reindeer AI
- Using Audit Trails and Reporting for Compliance Demonstration
Summary
For Graph App transmission issues, the key checks are connector configuration, mailbox permissions, trigger conditions, retry history, and the timestamps for affected messages or cases.
Comments
0 comments
Please sign in to leave a comment.