[Bug]: Execute Actions resulting in 404 Error is not handled in View Mode

[tomjose92]

Is there an existing issue for this?

• I have searched the existing issues

Description

With the Admin settings like Limit users to a single session or Session Timeout, there are cases where a user is not aware that the instance has already logged him out. If the App in View mode was already open in his Tab, he can go ahead and click buttons or other CTAs and nothing happens.
This leads to user frustrations as currently there is no error being shown on the App, stating that his session is timed out. Or he is not automatically taken to the login page.

This occurs only in View mode, in developer mode the user is automatically being taken to the login screen.

Steps To Reproduce

1. From the Appsmith Admin settings, enable the Limit users to a single session checkbox
2. Next open an App in View mode that has few actions connected to the widgets like buttons.
3. Now in another browser login to the same Appsmith instance with the same user credentials
4. Now go back to the previous browser and try clicking on any buttons or CTAs that would be triggering an API or Query

As you can notice, nothing happens on the UI layer and there is no error notification conveyed to the user as to what happened.
In inspect element you can see that the execute actions are giving a 404 Error.

Public Sample App

No response

Environment

Production

Severity

Medium (Frustrating UX)

Issue video log

No response

Version

Self Hosted 1.28