Articles in this section

Error: No connection found

Anitha Abraham
Updated

Error: Celigo does not receive EDI docs such as 850 from Target because of a No connection found error. 

Explanation: The Target connection fails because our AS2 routing is set to recognize the Receiver (To) ID as ECGRID. But, ECGrid pushes the Target traffic to Celigo with the Receiver ID TARGET_LORENDATA. (This issue could be because Target also uses ECGrid (LorenData) as their VAN gateway.)

Workaround: This issue needs to be resolved from the ECGrid side, and the steps are outlined below.

  1. Create a Celigo Support ticket with your Target issue details.
  2. Celigo will reach out to ECGrid via a Support ticket to update the outbound AS2 routing for you so that the "To" AS2 ID is changed from TARGET_LORENDATA to ECGRID.
  3. When you're informed that the change is made, you can resend the data to Target to check that the issue is resolved.