The Gmail Trigger Activity (first activity) fails, but only on my community org. So the trigger part seems fine, but the job immediately fails at the trigger activity. In the logs, it says “Email Received: An error occured in the activity.” (typo: occurred) But it doesn’t fail when I run it from Studio. The same package doesn’t fail when I run it from an enterprise-licensed org. It only fails when I run it from my org which is on a community license. I tried a couple of different robot VMs and got the same result. I’m using the same Gmail account, same package, same folder setup, and same robot VM image. The only difference I can see is Enterprise vs. Community. I checked the license page and I have plenty of API calls left. The logs on the robot VM don’t have any more detail. Any ideas?
Looks like some issues with the setup …
Better to add a log message with exception.stacktrace and exception.innerexception…these will give more info on ehat exactly is failing on the robot machines when they run
Cheers
@Anil_G I didn’t think I would be able to do that since a trigger activity like this one has to be the first activity in the main workflow. So there is no way to put a try-catch around it. But then I remembered the global exception handler and it did help. The detailed log messages showed that the out-of-the-box Robot role in Orchestrator is missing the View Connections privilege. All good now. Thanks for the idea.
Glad that it helped and you were able to resolve the issue…
Happy Automation.
Please close the topic if there are no further wuestions on this else happy to help
Cheers
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.