I have a process that exports SAP reports to Excel. the export works fine. the issue is that SAP opens Excel after saving the file. I use the Kill Excel activity to close Excel. but Excel takes to long to close and I get a timeout. I’ve tried extending the timeout to 15 seconds, but this doesn’t help. It is not an option to change SAP settings to prevent Excel from opening.
When I run the process in attended mode, the issue almost never happens. But when I publish to Orchestrator and have a bot run the process, this issue happens every time. The bot runs on the same VM used when running in attended mode.
That leads me to two questions:
- is there a best practice for closing Excel after it has been opened by another process (like SAP).
- Is there a way to determine if there is a problem (e.g., performance) with robot/job that is run through Orchestrator.