Workflows are always postponed until 12/30/9999

(0) Share

Report

Posted on by KGerth

165

I am on CRM 2011 for th elast couple of months. We upgraded form 4.0. All of our4.0 workflows and even new ones are always postponed until 12/30/9999. What is wrong? Am I doing something worng when creating th eworkflow?

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Mohammad Atif on at

Like (0)

Report

Can you please see if you can get more information following the steps: blogs.msdn.com/.../how-to-troubleshoot-system-jobs-failures-using-advanced-find.aspx

Also, can you see if the Async Service is running fine and the Service account under which the Async service is running is not locked? Restarting the Async Service is a good idea here

Capture the Async logs after creating a simple workflow and then see if there is any error message getting logged there. Make a note of the GUID of the Workflow and then search the logs with same GUId.

What is the update rollup installed in your CRM 4.0 servers

Was there any changes that has been done, after which you are facing this issue

Is this happening for all the users and for the user with system admin security role assigned ?

Thanks,

Was this reply helpful? Yes No
JohnLeme 355 on at

Like (0)

Report

IT has been a while. Hope you have already resolved your issue but if you haven't I came into this post while looking for the an answer and the issue in my case was that I was using process execution time instead of timeout. So you must use timeout for it to work properly.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

has anyone found a resolution to this yet? I have 5000+ workflows of which are postponed until 30/12/9999 23:59 some of these care completed workflows given, however i am trying to find out why this date is shown?

Was this reply helpful? Yes No
Matthew Martin 55 on at

Like (0)

Report

I have had this problem with 6 workflow process instances. Other instances for the same workflow work fine. The postpone until date should come form the date field of another entity, but in 6 cases this has not been picked up.

It seems strange that most of the time (>99%) this works fine, but for a few it put the postpone until field as 12/30/9999 11:59 PM.

Any comments or suggestion welcome.

Was this reply helpful? Yes No
Matthew Martin 55 on at

Like (0)

Report

I have the same thing happening, yet when I look at the system jobs and the status, many of the workflows with a postpone until of 9999/12/30 (US format for date) do execute any way.

Could this be misleading us into thinking that this is an error? It might be CRM's way of denoting to wait for some other condition.

Was this reply helpful? Yes No
Suggested answer

ScottDurow 21 on at

Like (1)

Report

Matthew - you are right. When a workflow enters a wait condition that is not date/time dependant it simply uses the Maximum Date to prevent the Async Service resuming it again. That is assuming of course that you are not using Dynamics CRM in 9999 ;)

Hope this helps,

Scott

1 people found this reply helpful.

Was this reply helpful? Yes No