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 1170 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 am encountering this same error in one of our dev vaults, while working on a new workflow that does have a bit of scripting, as well as a calculated "Name or title" property.  The error displayed calls out that property in a particular part of the workflow but not in other (earlier) parts.  So, I am trying to understand what specifically counts as a "script execution" -- is a workflow action that runs vbscript a single script execution, or is it each instance of a vault operation that might occur in the script?  Or something else?

    I appreciate any clarity on this so I can rework whatever needs reworking.

Reply
  • 0

    I am encountering this same error in one of our dev vaults, while working on a new workflow that does have a bit of scripting, as well as a calculated "Name or title" property.  The error displayed calls out that property in a particular part of the workflow but not in other (earlier) parts.  So, I am trying to understand what specifically counts as a "script execution" -- is a workflow action that runs vbscript a single script execution, or is it each instance of a vault operation that might occur in the script?  Or something else?

    I appreciate any clarity on this so I can rework whatever needs reworking.

Children
No Data
M-Files
M-Files Support


© 2025 M-Files, All Rights Reserved.