This Warning Event is part of all Web and Internet Actions (e.g., Get Webpage Content, Universal Web API Call).
Finished with warning…
Overview
The Operation for URL finished with warning Event indicates that the Web or Internet operation completed, but the server returned an HTTP response code configured to be processed as a warning.
The response was received successfully. However, the matching response code caused the Action to finish with a warning according to its Flow settings.
Event examples
See some examples of the Finished with warning Event messages:
- Task "Check service status" Action "Universal Web API Call" finished for "api.example.com/v4/check" with warning: 417 Expectation Failed · Server cannot satisfy Expect request header. [aw:66]
- Action "Get Webpage Content" finished for "portal.example.net:8080/content/status" with warning: 203 Non-Authoritative Information · Response modified by a transforming proxy. [aw:66]
- Action "Upload File to Website" finished for "uploads.example.com:8443/reports/20260923.zip" with warning: 507 Insufficient Storage · Server cannot store the resource. [aw:66]
- Action "Download File from Website" finished for "files.example.net/private/report.pdf" with warning: 401 Unauthorized · Authentication is required. [aw:66]
- Action "Save Webpage" finished for "docs.example.com/images/hero.png" with warning: 404 Not Found. [aw:66]
- Action "Submit Web Form" finished for "services.example.net/forms/request" with warning: 500 Internal Server Error · Generic server-side error occurred. [aw:66]
Cause
This warning occurs when the server returns an HTTP response code that matches one of the codes or ranges configured as warning in the Action's Flow settings.
Any HTTP response code can be treated as a warning when explicitly configured. For example, an expected 404 response can be accepted as a warning instead of being treated as an error.
Solution
Review the HTTP response code and message shown in the Event to determine whether the server response is expected.
If the response indicates an actual problem, such as authentication failure, a missing resource, or a server-side error, resolve the underlying issue and run the Task again.
If the response is acceptable for the workflow, open the Action's Flow tab and review the Process response codes configuration. Adjust the response codes or how matching responses are handled as needed.
Web
- Get Webpage Content · Overview · Events · 610200
- Upload File to Website · Overview · Events · 611200
- Download File from Website · Overview · Events · 612200
- Save Webpage · Overview · Events · 613200 · 613400
- Submit Web Form · Overview · Events · 614200
Internet
- Universal Web API Call · Overview · Events · 600200
Still have a question?
If you have any questions, please do not hesitate to contact our support team.