[Bug]: [Bug]: Editor frequently switches to "Save failed" when adding/configuring new Modal widgets, with inconsistent autosave behavior

[aahb93]

Is there an existing issue for this?

• I have searched the existing issues

Description

When building or editing an application in Appsmith CE, the editor frequently switches to "Save failed" while creating or configuring a new Modal and its child widgets.

This happens even though:

• the same application may already contain older modals with many widgets that work correctly,
• the issue can also reproduce in a brand new page and even in a new application,
• sometimes there is no obvious visible error at first,
• sometimes the same action initially fails, then later succeeds without a clear reason.

Observed behavior:

• adding a new Modal sometimes appears to work initially,
• but as soon as I add one or more child widgets inside the modal (for example Input, Select, Text, Button), the editor often switches to "Save failed",
• autosave becomes inconsistent,
• some states appear valid visually, but saving still fails,
• after some corrections, the same change may eventually save later,
• in some cases Debug shows binding / cyclic dependency / widget reference errors,
• in other cases the editor still shows "Save failed" even when no obvious bug is visible.

The editor frequently enters a "Save failed" state while working with new modals.
This can happen:

• when adding new widgets inside the modal,
• when configuring default values,
• when adding bindings,
• when wiring buttons/actions.

Sometimes the problem appears related to temporary invalid intermediate states during autosave.
Sometimes the same action later succeeds without changes that clearly explain the difference.
This creates uncertainty about whether the issue is caused by my bindings or by the editor/autosave process itself.

Important context:

• Existing older modals in some applications work correctly and contain many widgets.
• The issue appears mainly when creating NEW modals or adding NEW widgets inside recently created modals.
• The problem was reproduced in more than one workspace/application.
• The issue also persisted after trying a newer Appsmith version.
• Because this affects the editor/autosave workflow, it is difficult to determine whether every failure comes from a real binding error or from an unstable editor state.

This behavior makes the editor unreliable for modal-based form development.

I have already tried:

• upgrading Appsmith Community from v1.94 to a newer version,
• using another browser,
• reproducing the problem in another workspace,
• reproducing it in another application,
• creating new pages from scratch,
• removing problematic widgets and rebuilding incrementally.

The issue still persists.

Steps To Reproduce

1. Open Appsmith editor.
2. Create a new page or use an existing app page.
3. Add a new Modal widget.
4. Save/autosave may initially appear normal.
5. Add child widgets inside the modal (for example: Input, Select, Text, Button).
6. Configure simple properties such as:
   • default values,
   • labels,
   • onClick actions,
   • bindings to selectedRow or store values.
7. Observe that the editor often switches to "Save failed".
8. In some cases Debug shows:
   • cyclic dependency errors,
   • undefined widget reference errors,
   • type mismatch in default values,
   • linting errors in actions.
9. Even after correcting visible issues, the editor may continue to show "Save failed" temporarily.
10. Sometimes repeating the same action later allows save to succeed without a clear explanation.

Public Sample App

No response

Environment

Production

Severity

Low (Cosmetic UI issues)

Issue video log

No response

Version

Self Hosted 1.97

[linear]

APP-15038