Hi guys,
We have a custom workflow triggered on creation of email, first it was on background process. After converting it to Real-time, Emails stopped coming to MS CRM.
After converting to background, again emails are received. But I want the process to be in real-time. Kindly help me with your suggestion.
Thanks,
Vignesh M
*This post is locked for comments
Thank you so much Ravi, I ll try on demand workflow.
Like I said, It is possible that your code is working fine in dev but not in product due to the size of teh record or some other changes in your production.
I recently worked on an plugin issue which was working fine in dev but not in prod. Later I identified that there are other plugin on prod [PSA] which were also getting executed and causing a dead lock making my plugin to fail. I know this has nothing to with your issue, sharing just to tell you that there are various factor.
You need to ensure that your custom workflow works fine in prod or not. The best way s to execute it on demand on existing record and see if ti work or not.
Hope this helps
Yes Ravi, but why it differs from dev to production. Because same code is deployed.
Also, your actual issue is that the email is not received in CRM if you run the workflow as real time?
Then it must be your custom workflow which is failing on create of email which internaly failing to create the email itself.
As mentioned before, I would suggest to enable the on demand for the same workflow and see if ti works fine for any existing record. You don't need to change the existing trigger, just add the On Demand so that you can run the workflow n demand as well.
Yea Ravi, Same workflow works fine with real time in Dev.
Can you share a s screenshot of you workflow.
Did you say that tge same workflow is working fine in dev with real time?
We check two conditions owner and direction of the email. Ravi, its very urgent to fix this issue. Is it possible to make it work. Like mail should be received for synchronous workflow.
If it is still running as real time and you have the option Keep logs for workflow jobs that encounter error"" then you can see the process sessions if there are any failures.
It is possible that in custom code you are retrieving some values or updating which is taking more time and hence you see the issue only in prod.
The best option would be to test it by executing it on any existing record.
Do you have any any status reason check in your workflow?
Hi Ravi,
Its in production, cant test it now. I tried in Dev environment its working fine. It is possible to get any log files Ravi.
Thanks,
Vignesh
#1
Mohamed Amine Mahmoudi
83
Super User 2025 Season 1
#2
Community Member
52
#3
Victor Onyebuchi
6
Share
Report
All responses (
Answers (
