Hi everyone,
I read you posts with great interest, cause i have a such huge amount of workflows running at the same time and triggering on same and/or different field changes.. That there were some really ugly errors, if there were changes to field values of a huge amount of records.
I read about time limits, execution errors and stuff like that.
I thought of getting many more errors if a switch from async to sync???!!!
why do you think, chancing to async could reduce the errors...
do you surely know, that making a starter workflow, where i define the order of the executing sub workflows will be right if i use sync and if using async the execution order will be not right and they change to parallel execution?
hopefully you could help me too... I try to explain
I have a async starter wf which trigger fe. on field change
in this i decide the order of sub workflows
I do this because of the gotten errors.. Cause they were the result of trying to write things, but another wf tried to write things too.
if i had this all in sync there came errors because the execution time was to long.
Maybe one of the problems were, that there were 1500 records update (with webservice) in the same field, which triggered the starter wf
and I this starter wf there were other fields changed, which started another starter wf for this other field. And so on.
But are 1500 records really to much for crm??
Ok there were much follower field updates, but how else could i do this?
Thx.
Greets PeB
