We write code activities for Dynamics CRM in C# using the CRM SDK. After getting the OrganizationServiceProxy from the context we set its timeout to one hour like in the following code snippet.
IWorkflowContext context = codeActivityContext.GetExtension<IWorkflowContext>();
IOrganizationServiceFactory serviceFactory = codeActivityContext.GetExtension<IOrganizationServiceFactory>();
OrganizationServiceProxy service = (OrganizationServiceProxy)serviceFactory.CreateOrganizationService(context.UserId);
service.Timeout = new TimeSpan(1, 0, 0);
This worked well for us in the past years. But since update rollup ???? we experience that this timeout is in fact only around one minute long, which is often not enough for our operations. The operations themselves like create or update however are usually processed. The code activity just does not wait longer than a minute for its result.
Is this a new hard coded restriction of the Asynchronous Processing Service? Or can we configure this somehow?
