Error: Connection could not be established. Target service might be inactive.

Problem: The following flow runtime error is reported by several customers of integration apps. 

Connection could not be established. Target service might be inactive. [connect ECONNREFUSED xx.xxx.xxx.xx:xxx]

Reason: Upon investigation, we identified the problem is the downtime at the source or destination systems.

Note: By doing an IP lookup, verify the IP address in the error message to check if it belongs to Celigo or a third party.

Resolution: The system auto-retries the connection after 30 mins from when the error occurred. Once the connection is established successfully, the data gets synced to the destination application. If the first retry doesn’t resolve the error, the system retries three more times according to the following schedule.

• The second retry happens after one hour of the first retry
• The third retry happens after two hours of the second retry
• The last retry happens after four hours of the third retry

For example, if the error has occurred at 00:00 PM, the system retry happens according to the following schedule:

• 00:30 - first try
• 01:30 - second try
• 03:30 - third try
• 07:30 - fourth try

For most customers, the error is resolved on the first try. If the error persists, it should get fixed during a later try.