Answered by:
Workflows problem

Question
-
Hi,
I have two custom entities, each having related workflows.
The workflows of the first custom entity run normally, as for the workflows of the second one, they are not working.
What could be the reason?
Any idea?
Friday, July 11, 2008 1:12 PM
Answers
-
Hi,
The solution was to put the scope of the workflow as Organization.
Pretty easy right?
Thursday, October 16, 2008 6:43 AM
All replies
-
Is the scope of the workflow set to 'Organisation' or just 'User' as this is a common error when setting org-wide workflows?
The other place to look would be in the workflows themselves and system logs to see if there are errors being produced there.
Leon TribeMonday, July 14, 2008 12:04 AM -
did you import this environment through deployment manager? If so, there is a bug where the asynchronous service does not process workflows properly, and there is a hotfix
http://support.microsoft.com/kb/950680
Monday, July 14, 2008 12:28 AMModerator -
Hi, my workflow is a user one not an organization one and i didn't deploy it using the deployment manager. i just imported it. All my other workflows are working. i tried to rebuild this one but still it isn't working. Any idea how to make it work?
Thanks
Monday, July 14, 2008 8:10 AM -
If you tried all of that, I would set up a case with Microsoft. They can help you solve this.Monday, July 14, 2008 11:19 AMModerator
-
Now i noticed that the workflows that were working are not anymore. Only the On demand workflows are working.
Any idea how to fix this?
Monday, July 14, 2008 12:10 PM -
Monday, July 14, 2008 12:26 PMModerator
-
But i didn't use the deployment manager.
Monday, July 14, 2008 12:48 PM -
i just noticed that when i trigger the workflow, it's not showed in the workflow part and the record it should create is not created but a system event named "Workflow Expansion Task" is createdand whose Owner is the System. It's status reason is Succeeded. Is this information helful for anyone so he can help me?
Thanks in advance
Monday, July 14, 2008 1:49 PM -
Hi,
The solution was to put the scope of the workflow as Organization.
Pretty easy right?
Thursday, October 16, 2008 6:43 AM -
This was the common error I was referring to
I'm glad you got it sorted out.
Leon TribeWant to hear me riff on about all things CRM? Check out my blog
http://leontribe.blogspot.com/Sunday, January 11, 2009 8:33 PM