Error “The maximum number of script executions for a single operation has been reached” when importing from a linked network folder

I have only ever seen this when there's some script involved.  I don't think that automatic workflow state transitions count.  If there really is no scripting then I would perhaps raise this with support.

Raising that AVS setting is a sticking plaster ("bandaid", for my American friends).  Typically it's not a good practice to do it.  It means that transactions can stay open longer, meaning that there's more chance of database errors, and potentially slowing database access for users.  Also: what do you do when you hit that ceiling again?

I have only ever seen this when there's some script involved.  I don't think that automatic workflow state transitions count.  If there really is no scripting then I would perhaps raise this with support.

Raising that AVS setting is a sticking plaster ("bandaid", for my American friends).  Typically it's not a good practice to do it.  It means that transactions can stay open longer, meaning that there's more chance of database errors, and potentially slowing database access for users.  Also: what do you do when you hit that ceiling again?

From memory I do believe that workflow actions count. I have a couple of customers where it was necessary to raise the limit.While I agree with the concerns it is sometimes necessary and relevant to change this setting. But obviously it should only be raised to the point necessary in the case at hand.

You may be right here Karl, I honestly don't recall for certain.

I did want to add that general point about raising the limit though: in my previous life I've come across many situations where this has been done blindly to resolve errors, then had to be revisited later due to the knock-on effects of doing so.