As this has nothing to do with any scenario or module settings, I would consider this a bug.
For complex technical issues or bugs like this, directly contacting support can often lead to a faster resolution. They have access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to. Additionally, sharing sensitive information about your situation might not be suitable for an open forum discussion.
If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.
Directly contacting support will lead to a faster resolution. This is because as it is a bug, there is nothing we can do to resolve it. They have access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to. Additionally, sharing sensitive information about your situation might not be suitable for an open forum discussion.
I see that you opened a ticket with us and that the support team investigated this and gave you the following advice. I’m sharing it here for the benefit of the community.
Make Support response:
Looking at your scenario history, the error response is handed over directly by One Drive, please try using the other trigger highlighted in the screenshot below and let us know your observation.