Workflow timeout is postponed till 12/30/9999

(0) Share

Report

Posted on by Community Member

Hello,

I have a workflow running in the background which is designed in the following manner:

1) Event is triggered on the change of a field in a entity called "Event"
2) Once triggered, the initial step of the workflow is to timeout until 2 hours after a date field called end date.(Contains both date and time )
3) Checks a few conditions(One of the conditions is to check if the end time < process execution time) and if met, they do certain actions.
4) Stop workflow with status succeeded.

This workflow is very inconsistent in its working. I have observed that this workflow is failing when the end date(time) is the same for multiple records in the event. If that's the case, then it is executing succesfully for one record and failing for the others. For the failed records, the workflow is postponed till 12/30/9999!
The workflow executed successfully for another record which has a differed end date(time).
I also got the error "An error has occurred. Try this action again. If the problem continues, check the Microsoft Dynamics CRM Community for solutions or contact your organization's Microsoft Dynamics CRM Administrator.
Finally, you can contact Microsoft Support."

There is no error in the logic because the records which failed and which passed are almost exactly the same.

Suggestions?

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Wayne Walton 13,730 on at

Like (0)

Report

On the failed workflows, the 9999 date is a way of saying "this is invalid, it will not recur". Also, on the failed workflow record itself, there is a Details tab. Open that up and it will give you a trace of exactly what failed.

Post that error here if it's not immediately clear what the problem is.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hello Wayne,

Thanks for the response. Here is the message:

nhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]

: Message name 'RetrieveMultiple' does not exist.Detail:

<OrganizationServiceFault xmlns:i="www.w3.org/.../XMLSchema-instance" xmlns="schemas.microsoft.com/.../Contracts">

<ErrorCode>-2147220989</ErrorCode>

<ErrorDetails xmlns:d2p1="schemas.datacontract.org/.../System.Collections.Generic" />

<Message>Message name 'RetrieveMultiple' does not exist.</Message>

<Timestamp>2017-06-09T01:00:04.1968497Z</Timestamp>

<InnerFault>

<ErrorCode>-2147220970</ErrorCode>

<ErrorDetails xmlns:d3p1="schemas.datacontract.org/.../System.Collections.Generic" />

<Message>System.ArgumentException: Message name 'RetrieveMultiple' does not exist.

Parameter name: messageName</Message>

<Timestamp>2017-06-09T01:00:04.1968497Z</Timestamp>

<InnerFault i:nil="true" />

<TraceText i:nil="true" />

</InnerFault>

<TraceText i:nil="true" />

</OrganizationServiceFault>

at Microsoft.Crm.Extensibility.OrganizationSdkServiceInternal.RetrieveMultiple(QueryBase query, CorrelationToken correlationToken,

CallerOriginToken callerOriginToken, WebServiceType serviceType, Boolean checkAdminMode)

at Microsoft.Crm.Extensibility.InprocessServiceProxy.RetrieveMultipleCore(QueryBase query)

at Microsoft.Crm.Workflow.ObjectModel.WorkflowAssemblyResolverHelper.RetrieveActivityNameAndGroupName(String assemblyQualifiedName, String& activityName, String& activityGroupName,

ICommonWorkflowContext context)

at Microsoft.Crm.Workflow.ActivityHostBase.AddPluginTrace(Activity customActivity, Exception exception, ICommonWorkflowContext context)

at Microsoft.Crm.Workflow.ActivityHostBase.OnWorkflowTerminated(WorkflowApplicationUnhandledExceptionEventArgs args, WorkflowApplication activityInstance, ICommonWorkflowContext context)

at System.Activities.WorkflowApplication.UnhandledExceptionEventHandler.OnStage1Complete(IAsyncResult lastResult, WorkflowApplication instance, Exception exception, Activity source,

String sourceInstanceId)

at System.Activities.WorkflowApplication.UnhandledExceptionEventHandler.Run(WorkflowApplication instance, Exception exception, Activity exceptionSource, String exceptionSourceInstanceId)

at System.Activities.WorkflowApplication.OnNotifyUnhandledException(Exception exception, Activity exceptionSource, String exceptionSourceInstanceId)

Was this reply helpful? Yes No
Suggested answer

Andreas Cieslik 9,267 on at

Like (0)

Report

Have you check these best practices:

www.magnetismsolutions.com/.../workflow-wait-conditions-best-practices-dynamics-crm-2011

Timeout in combination with process execution time could be issue here (check article in link above)

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hello Andreas,

Thanks for the response. I have read the blog you sent me a link to, before. The workflow is designed the way it is and I don't think there can be a workaround for this particular case am working on.

Was this reply helpful? Yes No
Swift but Sincere 82 on at

Like (0)

Report

I guess I'm seeing that any waiting process that is not waiting for a datetime shows this way. So it seems most every Business Process that is waiting at a step for data entry shows up in the suspended jobs view of the system jobs log. This is not a useful presentation.

Was this reply helpful? Yes No