Office 365 Create Event activity works in Studio but not unattended

Hi everyone,

I’ve recently published a short automation that uses the Microsoft Office 365 Create Event activity. The process runs without any issues in UiPath Studio, but I’m unable to get it to work when running the process from Orchestrator. When I try to execute the process unattended via Orchestrator, I receive an error that isn’t very informative (see screenshot below).
The image shows a log with an error and an info message indicating that unspecified errors have occurred in creating an event and an Office365Exception. (Captioned by AI)

I’ve checked the package requirements, and the activity shows up as “Unknown” status but according to UiPath’s documentation, this shouldn’t prevent the process from executing successfully. Orchestrator - Managing Package Requirements
image

Does anyone know the potential cause of this issue or would there be any suggestions for troubleshooting? I’d really appreciate any help or insights, as I’ve been troubleshooting for hours without progress.

Hi @laxfree

Could you please wrap the Create Event in a Try Catch, and in a Catch log the stack trace of your error?

Something like this:

It would help us investigate the issue.

Hi @loginerror, thank you for your response and really appreciate your help on this! Here’s a screenshot of what I’m getting.

This seems odd. I’ve checked the permissions on the connections and I believe it has all of the permissions required even Calendars.ReadWrite and Calendars.ReadWrite.Shared

Service has a connected status as well.

Thank you. Could you please add your current version of the Microsoft 365 activity package that is being used in this project? (completely forgot to ask about it)

No worries, you’re fine, I am currently using version 3.0.14 for Studio and the published process uses the same version as well.

Just to confirm, would it be possible to also validate with the latest versions as well?

There have been a few since the 3.0.14 release:

Could you please validate with the latest GA 3.1.21, and also with the latest preview 3.2.0-preview?

Additionally, it seems like the exception stack that we got with the Try Catch is not enough for us to narrow down the issue. Could you see if there is an icon next to this message in Orchestrator to look into the log message and hopefully extract the inner message?

Yes, I just tried both versions the latest and even the pre-release preview 3.2.0 and unfortunately, I’m still encountering the same issue.

There is an inner message, but I don’t think it’s informative. Was there a specific piece of information in the inner message you were looking for?

image

image