Changed Request
A changed request is referred to within Spider as an RFC (Request Failed Changed). There can be several reasons why a request gets this status.
Business Rule
It can happen that a robot characterizes a request as failed, while according to the business rule it is a success case.
Planned task
An operator has entered a scheduled task and it needs to be modified or deleted. Without the ability to convert a request to RFC, this unperformed task would be labeled as an error.
Manual action
- A request has been handled incorrectly by the robot.
- An operator has manually adjusted the request.
An operator decides to drop one or more requests from the Todo list. These dropped requests can also be found under Changed requests.
Adjust RFC
You might want to adjust a request for the following reasons:
- Even if the robot or operator has marked the request as failed, it could be that the operator manually processed the request. Therefore, the request has been successfully processed, but through manual intervention.
- In the Mtinfo, this could provide a distorted view and be marked as a failure, while the request may ultimately have been successfully processed.
- Another option is to add information to the request explaining why it was manually marked as failed.
- This approach provides a clear track and trace within a request, ensuring transparency and clarity in the process.
Navigate to More > Changed Requests > Maintain in the menu and change the corresponding request.
In the example below, we set a remark on the request (1). Be clear on your comments you add, so other understand what was wrong or when the request was processed manually. Then save the RFC (2).
Overview RFC
To see an overview of all requests that have been changed (RFC) go to Requests > Changed in the spider menu.
Click on the "+" icon(1) to expand the request. We see the Remark we added(2) an operator has entered in the RFC.
