[Bug]: Action execution should only trigger after all entities are saved

[ame-appsmith]

Is there an existing issue for this?

• I have searched the existing issues

Summary

Body + update action one set has to finish before the second set of body + update action occurs.

Context: The user is getting the message Appsmith Server is taking too Long to Respond when editing JS Objects or working in the Page editor with widgets. It happens when saving or just loading queries.
The root cause is that the JS Object did not finish saving before the user tried to execute another action. To work around this problem, when the saving of a particular JS Object is still in progress, users need to wait until it finishes before moving to another page/entity or making new changes in the UI.

More information in this ticket and Slack thread.

Why should this be worked on?

We need to improve the user experience if the JS Object that was edited is not saved yet when a new action is done.

[nghialm269]

Hi, I've been seeing the same message (Appsmith Server is taking too Long to Respond) a lot recently while working on my app.

Whenever I edited a jsobject file (~300 lines), a Saving spinner showed up at the top, and the message appeared after a while (I guess the save request timed out after 20s or so).

After too many timeouts like that, the code editor refreshed itself (it scrolls to the top) and my changes were lost.

I've tried to split the jsobject file into smaller files as advised, it helps a bit but not too much.

For some more context, when I tried to create a new jsobject in the same app and add a new line, it took ~3s to save. This app has 2 jsobject files with 300 lines, 1 with 100 lines, and 4 with 50 lines.

When I tried the same with a smaller app (1 file with 15 lines), it took ~300ms to save.

[rishabhrathod01]

This issue title and description got mixed up of multiple different issues, i have create separate issues for each problem

• JSObject update taking too long - [Epic]: Resolve the JS Object update timeout issues #35542
• Creation of identical names JSObject - [Bug]: Creation of indentical name JSObject in a page #35385