We built an automation process to be run in the VM based on email event trigger whereas the orchestrator started another job after the job got completed. Recreating the trigger solved it, but few processes later the same issue occurred again. Kindly assist on how this can be resolved. Thank you.
This issue usually occurs when the existing trigger metadata in Orchestrator becomes corrupted or desynchronized after multiple executions. Recreating the trigger refreshes its configuration and resolves the inconsistency. Itâs also recommended to verify that no duplicate triggers or conflicting schedules exist for the same process.
Yes, it is running the multiple jobs for the same email being received. The email details are confidential, so I can share them. But I have 2 jobs for the same email. I even tested it out to re verify it
Thanks for the input. Is it possible to remove the metadata or cache at the end of each trigger or process. As we have process running for 10 days with the same trigger email coming it.
Yes, you can clear metadata or cache at the end of each process by adding cleanup steps in the âFinallyâ block of your workflow. This ensures all temporary data, files, and variables are reset after every trigger execution.
No, including cleanup steps in your workflowâs Finally block will only clear temporary files, variables, or cached data within that process. It does not reset or clear the trigger metadata in Orchestrator itself. Trigger configurations, schedules, and history remain intact unless you manually delete or recreate the trigger in Orchestrator.
The input arguments dont share any confidential information.
The email ID is effectively a random set and letters and numbers. It can also try to help identify what triggered the job.
I have heard of this âcache problemâ being mentioned by the other poster, and dont see how doing anything in a workflowâs finally block could be remotely related, so am not sure on the credibility of that answer and would be curious to see some reference for this âcorrupted metadataâ on a trigger.
There is not input argument for the job, When I a new email arrives in the inbox with a subject line equal to â[Internal Trigger] Send reminders to Certifiersâ it starts the job
Its the jobs input arguments, you view any job and view the details, which can show the input arguments. We want to try to compare 2 jobs that you say are for the same email that has been triggered twice.
There are different Event Object IDs (this is the ID of the email) and different event IDs (indicating they are different events).
So this is indicating that 2 emails are detected, not one, so two events get fired.
If you for sure only have one email coming in, then you need to check deeper on the mailbox. It sounds like you are getting at least 2, perhaps there is some sort of rules or settings on your mailbox, perhaps moving or copying emails, that are making it appear as two emails?
You can use those Object IDs to retrieve the emails and see what the difference between them are?