IntegrationHub action fails with error "failed because no valid MID is available,Please check System Logs".

IntegrationHub action fails with error "failed because no valid MID is available,Please check System Logs".

All currently supported releases.

IntegrationHub lets you build reusable integrations with third-party systems and call them from anywhere in the platform. For example, request IntegrationHub to call external systems using integration APIs from the Action Designer Script step, run the Script step on the Mid Server, and activate protocol steps like REST, SOAP, and PowerShell.

The integration will need to determine what MID server to use, if the integration is set to use a MID server. If based on the configuration a MID server cannot be found, the error "failed because no valid MID is available,Please check System Logs" will be returned.

1. Review the integration configuration. If for example a http request, review the connection configured.
2. Update the action criteria for the MID server. Alternatively, update the MID server capability, application, and ip range so that it can be found by the action.

• IntegrationHub
• Introduction to credentials, connections, and aliases
• MID Server selection