Answered by:
Any Issues Experienced With Long Workflow Wait Conditions?

Question
-
I have a client who is considering implementing 6-month long wait conditions for one of his workflow steps for his On-Premise CRM 4.0 instance. Has anyone had issues with wait conditions this long? I'm curious if anyone has experienced performance or reliability issues where long wait conditions stall out when the async service is overburdened.
Thanks!
Phil
Phil Edry – Altriva Solutions – http://www.altriva.com/AltrivaBlog.aspxWednesday, August 18, 2010 7:17 PM
Answers
-
Hi Phil,
waiting workflow does not consume any memory resources and CPU so you should not face any issue for that
refer this Post for your reference
Mahain : http://mahenderpal.wordpress.com- Marked as answer by Phil Edry Thursday, August 19, 2010 6:15 AM
Thursday, August 19, 2010 3:42 AMModerator -
HI Phil
Workflow saves in database
the async system job only executes those work which execution time is in time frame
so dont worry
it will not affect on Performance
Nikkas MIcrosoft Dynamics Crm 4.0 Technology Specialist- Proposed as answer by Nika MSD CRM Expert Thursday, August 19, 2010 4:43 AM
- Marked as answer by Phil Edry Thursday, August 19, 2010 6:15 AM
Thursday, August 19, 2010 4:43 AM
All replies
-
Hi Phil,
waiting workflow does not consume any memory resources and CPU so you should not face any issue for that
refer this Post for your reference
Mahain : http://mahenderpal.wordpress.com- Marked as answer by Phil Edry Thursday, August 19, 2010 6:15 AM
Thursday, August 19, 2010 3:42 AMModerator -
HI Phil
Workflow saves in database
the async system job only executes those work which execution time is in time frame
so dont worry
it will not affect on Performance
Nikkas MIcrosoft Dynamics Crm 4.0 Technology Specialist- Proposed as answer by Nika MSD CRM Expert Thursday, August 19, 2010 4:43 AM
- Marked as answer by Phil Edry Thursday, August 19, 2010 6:15 AM
Thursday, August 19, 2010 4:43 AM