An HTTP 503 error indicates that the destination server (the new host) is not ready to handle the request. This typically points to an issue with the target environment or network connectivity rather than with Cortex itself.
Confirm that the target endpoint is publicly accessible or reachable from the Cortex environment. Check for DNS resolution issues or network restrictions that might block traffic from Cortex to the destination host. Review any firewall or security group rules to ensure Cortex has permission to send requests to the endpoint.
If Cortex cannot resolve or reach the host, you may see 503 errors and no incoming traffic on your end. These conditions must be corrected in the target environment before Cortex can successfully execute the workflow.
For more information, see Workflows documentation.