When connecting to a web service from Etlworks, you may encounter one of the following common HTTP errors:
404 not found
- Reason: The requested URL or resource could not be found.
- Solution: Double-check that the URL is correct and that the resource exists at that location.
403 Forbidden or 401 Unauthorized
- Reason: The request is not properly authenticated or lacks the required permissions.
- Solution: Ensure authentication is correctly configured in the HTTP connection (e.g., API key, OAuth, Basic Auth).
502 Bad Gateway
- Reason: The server received an invalid response—typically due to a network or proxy configuration issue.
- Solution: Enable auto-retries in the HTTP connection to handle intermittent failures.
504 Gateway Timeout
- Reason: The request took too long to complete and was terminated by an intermediate server.
- Solution: The default HTTP timeout in Etlworks is 1 hour. If needed, increase the timeout for the HTTP Connection.
500 Internal Error
- Reason: The web service encountered an unexpected condition and could not complete the request.
- Solution: This is an issue on the server side. Contact the provider or owner of the web service to investigate the root cause.