ECGrid Connector: Documents Not Appearing in Simplify

Overview

When an ECGrid connector is set up in Simplify, a callback (webhook) is automatically registered on the associated ECGrid mailbox. This callback is how ECGrid notifies Simplify in real time when a new document arrives in the mailbox — it is the trigger that kicks off document processing.

However, if a document was delivered to the ECGrid mailbox before the Simplify connector was created, the callback did not exist at the time of delivery. ECGrid fired no notification, Simplify never received the document, and nothing appeared in Flow Activities. The document is not lost — it is sitting on the mailbox — but Simplify has no awareness of it.

The fix is to resend the document from the ECGrid Portal. Once resent, the callback fires, Simplify picks it up, and the flow processes normally.

How the Callback Works

Trading Partner sends EDI

        │

        ▼

ECGrid mailbox receives document

        │

        ▼

ECGrid fires callback (webhook) → notifies Simplify

        │

        ▼

Simplify pulls document and processes it through the flow

The callback is created on the mailbox at the time the ECGrid connector is saved in Simplify. There is no retroactive notification for documents that arrived before that point.

Symptom

• The ECGrid connector is configured and the flow is enabled in Simplify.
• The trading partner confirmed they sent the document.
• The document shows as delivered in the ECGrid Portal (visible under Transactions).
• Nothing appears in Simplify Flow Activities for that document.
• No errors in Simplify — the flow simply never ran.

Root Cause

The document arrived at the ECGrid mailbox before the Simplify connector was created. Because the callback did not yet exist when the document landed, ECGrid had no webhook endpoint to notify. Simplify was never informed the document was there.

This is a timing issue, not a configuration error. The connector, flow, and mailbox can all be set up correctly and this will still occur if a document arrives before the connector is saved for the first time.

Resolution

Resend the document from the ECGrid Portal. This re-triggers the delivery event, the callback fires, and Simplify processes the document through the flow.

Steps to Resend from the ECGrid Portal

1. Log into the ECGrid Portal.
2. Select Transactions from the left-hand navigation panel.
3. Enter the appropriate search filters (date range, trading partner, ISA control number, etc.) and select Search Transactions.
4. Locate the document(s) that need to be resent.
5. Check the checkbox on the left-hand side next to the ECGrid Message ID for each document. To select all results, use the top checkbox.
6. Select Resend Selected in the top-right corner.
7. The document will be retransmitted. The callback will fire and Simplify will pick it up for processing.

After resending, verify the document appears in Flow Activities in the customer's Simplify account.

Prevention

To avoid this issue during onboarding or testing:

• Create the ECGrid connector in Simplify before asking the trading partner to send a test document. The connector must be saved first so the callback is registered on the mailbox.
• If a trading partner insists on sending before setup is complete, note the date/time so you can quickly locate and resend the document after the connector is configured.
• After creating the connector, confirm the callback is active by checking the mailbox configuration in the ECGrid Portal before initiating any test transmissions.