This Error Event is part of Get Webpage Content Events.
Event ID · 610400
Overview
The error indicates that the Get Webpage Content Action failed to retrieve content from the specified URL. It may be preceded by additional error messages that provide more detailed information about the cause of the failure.
Event examples
See some examples of the URL retrieving failed Event messages:
- Task "Website content check" Action "Get Webpage Content" failed for "https://content.invalid/status" with error: Could not resolve hostname. [aw:79,6]
- Action "Get Webpage Content" failed for "http://api.invalid/v1/status" with error: Could not resolve host: api.invalid. [aw:4]
- Failed for "https://portal.example.com:8443/reports/export?selection=all" with error: 414 Request-URI Too Large. [aw:5]
- Failed for "ftp://files.example.net/archive/report.csv" with error: unsupported protocol scheme. [aw:2]
- Failed for "https://api.example.com:8443/v4/data?mode=full" with error: Error in the HTTP2 framing layer. [aw:79,16]
- Failed for "10.0.0.25/status" with error: Timeout was reached. [aw:79,28]
- Failed for "https://10.0.0.42:8443/health" with error: Operation timed out after 3004 milliseconds with 0 bytes received. [aw:4]
- Failed for "portal.example.net:8443/reports/latest?view=full" with error: 302 Found · Resource temporarily available at another location. [aw:5]
More examples…
Internet and web-related Actions can encounter a wide range of errors originating from the local system, network, or remote service. Depending on the configuration and operation, additional Event messages may report general, authentication and OAuth, SSL/TLS, file, connection, and other related errors.
For the Get Webpage Content Action, failures can occur at different stages of the request—for example, when a host cannot be resolved, a connection times out, a redirect cannot be followed, or the remote server returns an HTTP error. Review the accompanying Event messages and error details to identify the underlying cause.
Solution
Review the error details and any preceding Event messages to determine the cause of the failure. Verify the URL, network connectivity, Web Profile settings, authentication, and other request options as applicable. Also ensure that the remote server is available and accepts the configured request.
Note
Due to the variety of errors that can occur while retrieving web content, the exact Event message depends on the underlying failure. The examples provided are not exhaustive.
Ask for more…
If you have any questions, please do not hesitate to contact our support team.