Hi Himani,
When a BP process runs, a Log is created. These logs can be found in ControlRoom by right clicking on a case in the Work Queue for the process and choosing 'View Log':
Studying the log should give you a hint of what actions in your process are no longer working as expected and if any Exceptions appear that tell you where things go bad. If you select everything in the log and copy it, you can paste it to an XL that provides better view and easier selections. Note that a Log can consist of multiple pages of 1000 rows and you error may be found on another page then is opened by default.
The next step would be to step through your process to the suspicious action to see what is going on there. Is there a parameter mismatch? Some invalid value? No authority? Sometimes you can start right away where you expect your error to be, but often you have to start from the beginning as the steps preceding the error are required to continue. The better you know your process, the easier it is to determine what has to run and what can be omitted.
As you seem to have found that nothing can be downloaded, that should be a solid hint where to start looking. Why can it no longer download? Has the website where you download from perhaps changed? Can it still be accessed and logged on to by the process? Can the process still navigate on the website?
In the end, there's usually a good lead to the error in the Log, and stepping the process usually is the easiest way to reproduce the error. Sometimes this does not work, but more often that not it does.
Try the above and then get back to this forum with more specific information, eg what action is no longer working and exactly what exception is thrown.
Notes:
------------------------------
Happy coding!
Paul
Sweden
------------------------------
When a BP process runs, a Log is created. These logs can be found in ControlRoom by right clicking on a case in the Work Queue for the process and choosing 'View Log':
Studying the log should give you a hint of what actions in your process are no longer working as expected and if any Exceptions appear that tell you where things go bad. If you select everything in the log and copy it, you can paste it to an XL that provides better view and easier selections. Note that a Log can consist of multiple pages of 1000 rows and you error may be found on another page then is opened by default.
The next step would be to step through your process to the suspicious action to see what is going on there. Is there a parameter mismatch? Some invalid value? No authority? Sometimes you can start right away where you expect your error to be, but often you have to start from the beginning as the steps preceding the error are required to continue. The better you know your process, the easier it is to determine what has to run and what can be omitted.
As you seem to have found that nothing can be downloaded, that should be a solid hint where to start looking. Why can it no longer download? Has the website where you download from perhaps changed? Can it still be accessed and logged on to by the process? Can the process still navigate on the website?
In the end, there's usually a good lead to the error in the Log, and stepping the process usually is the easiest way to reproduce the error. Sometimes this does not work, but more often that not it does.
Try the above and then get back to this forum with more specific information, eg what action is no longer working and exactly what exception is thrown.
Notes:
- When you say 'script' I assume you mean a BP process.
- Most likely something broke in the reinstall of BP or the computer it runs on, but still the procedure as described above should lead you to what it is that is broken.
------------------------------
Happy coding!
Paul
Sweden
------------------------------
Hi Himani,
Before checking the session logs from Control room, You must ensure that staging logging is enabled for your process.
If the stage logging is set to "Errors Only" , you will only see those action stages where exceptions or errors have occured.
For detailed session logs and better analysis or troubleshooting, session logs has to be enabled for all stages. You have to execute the process again after enabling stage logging. You can do the same as mentioned below.
------------------------------
Saurabh Goswami
RPA Architect
Ericsson
------------------------------
Before checking the session logs from Control room, You must ensure that staging logging is enabled for your process.
If the stage logging is set to "Errors Only" , you will only see those action stages where exceptions or errors have occured.
For detailed session logs and better analysis or troubleshooting, session logs has to be enabled for all stages. You have to execute the process again after enabling stage logging. You can do the same as mentioned below.
------------------------------
Saurabh Goswami
RPA Architect
Ericsson
------------------------------
