The error indicates that the platform is blocking saves because too many save-related actions or events are being triggered on the form in a short period, so the save operation is effectively being canceled.
In similar Microsoft form-based environments, this typically happens when:
- A save event is triggered again before the previous save completes.
- Custom logic or scripts attached to the save event are calling save repeatedly or at the wrong time.
In model-driven apps, for example, this is seen as a Saving in Progress error when the OnSave event is called again before the previous OnSave finishes, often due to code that calls save() inside an OnSave handler or via setTimeout() that overlaps saves. This causes recursive save loops and prevents the record from being saved.
To troubleshoot in a similar scenario:
- Review any custom logic that runs when the form is saved (for example, event handlers or scripts) and remove or adjust any code that calls save again from within an
OnSave-type event.
- Ensure there are no concurrent or repeated save calls (for example, timers or auto-save logic) that might overlap.
- Use the platform’s monitoring or diagnostics tools (such as Monitor and form checker in model-driven apps) to inspect the
OnSave call stack and identify which script or function is causing repeated or unsupported save calls. Then work with the script owner to correct it.
If the form or record is not saving at all, also check whether any save event handler is explicitly canceling the save (for example, by calling a preventDefault()-style method on the save event arguments).
If there is no custom logic or scripting on the form, contact the form owner or administrator and provide them with the exact error text and what actions were taken before it appeared so they can inspect any underlying save logic or platform issues.
References: