Edit: I had some extra conserns, so a few more questions were asked. Also I had to try it in practice. I had to put a little delay while the process was waiting for the excelfile to entirely save before I killed Excel. It now works. Below you’ll find the solution from @Palaniyappan. Thanks
Hi, friends. This again…
There are some forum entrys on this matter, but none of them seems to solve my problem.
Below you can see a message from my Orchestrator log.
My excel file is in fact not open, but may hang back (delay) from earlier entrys?
What type of message is the message (red marking), and is it possible to obtain this message, so I could use the message in e.g. a Retry scope?
Thanks, @Palaniyappan .
But what if the recently excel approach actually is not ready? It could be that the message/situation is legit? If that is the reason for the message, it would be scary til kill the process?