I noticed that my Integration Service Connection for Outlook 365 (Individual) account does not work at runtime from a UiPath process
Here are the specifics of the problem.
The Integration Service Connection is created without issues in Automation cloud.
Connection test is successful
The connection is accessible in a UiPath project
However, when the project is run, the Integration service fails!
In this particular case, the same outlook.com account is used to login to the Automation Cloud.
When I performed a similar test in another Automation Cloud instance that does not use outlook.com to login, the Integration Service worked as expected.
I am not sure if this is an issue with my outlook.com account, or the Automation Cloud instance.
If you can conduct a similar test and clarify, that would be very helpful.
Fair enough, there is an annoying (basically undocumented by both Microsoft and UiPath) scope you need to include that allows the connection to stay alive, since you could make an initial connection then it broke it sounded similar, but if you use the vanilla connection method it shouldnt be the issue as only in ‘bring your own’ can you change the scopes.
I’ve been repeating, as often as I can, to the product owners of the IS via our MVP channels, that they urgently need to add some sort of logging and error messages to it so we can actually see why it disconnects etc aswell as do the documentation properly.
They have indicated they are intending to add better logging, but its hard to get clarity on when we will see it.
I know that doesn’t help you in the short term, but hopefully in the medium term its going to improve to the point where we can actually debug these sort of things.
Agreed. The fix if any won’t be quick. But at least it may help avoid situations like the one i created for myself.
In the near term it would be great to know if using the same account in two ways as I have is truly a problem in the product or if it’s just a freakishly random outlier in my case.