Discover M-Files Workspaces: All work available in the right business context, automatically!
➡️ Learn How it Works

Options
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 9 replies
  • Subscribers 19 subscribers
  • Views 1308 views
  • Users 0 members are here
Related

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

Anne BC

Hi everyone,

We’re observing a strange behavior in one of our vaults and would like to know if anyone has seen something similar.

When importing documents via a linked network folder connection, some files (not all) trigger the following error:

The maximum number of script executions for a single operation has been reached for the object.

The confusing part is that no scripting logic is configured in the vault:

  • No Property Calculators,

  • No Automatic Values,

  • No Event Handlers,

  • No VAF applications.

All previous scripts were removed, the server was restarted, and the linked connection recreated — yet the issue persists on most imported files.
A few files are imported normally, while others consistently produce this error.

Has anyone experienced something similar, or can explain what internal process might still trigger repeated “script executions” in this context?

We’re running M-Files Server 25.10.15296.12

Thanks in advance for any insights or experiences you can share!


— Anne

Parents
  • 0

    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?

  • 0 in reply to Craig Hawker

    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.

  • 0 in reply to bright-ideas.dk

    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.

Reply Children
No Data
M-Files
M-Files Support


© 2025 M-Files, All Rights Reserved.