Not when the automation moves the files. That works perfectly. A couple of scenarios allowed me to reproduce the error:
- Another user of shared inbox (or same user of machine where bot runs) manually moves an unread message from one shared folder to another (as long as that email fits the criteria of emails the automation is supposed to move)
- Another user (or same user of machine where bot runs) manually deletes an email that fits the criteria of emails the automation is supposed to move)
After a couple more hours of testing with the exception handling i shared earlier, the error returned once more. Earlier today i saw the bot recover from error with the original Argument Exception sequence, but as of right now, even that action didnt suffice. I just added a “Close application” and then “open application” for outlook to the Argument exceptions sequence, and the bot is again recovering without problems. This has been quite a tricky issue to diagnose.