[Feature]: Need a way to terminate actions that are run automatically or indefinitely

Is there an existing issue for this?

[X] I have searched the existing issues

Summary

Currently, when any action causes an app to go into an unusable state, there is no way to terminate code execution from front end i.e. UI. This causes users to contact support and request a resolution which is done by either tweaking backend or getting on a call to debug the issue requiring manual intervention each time a user hits a dead-end with their app due to faulty code.

Instead, having a UI capability will allow users themselves to debug and salvage any code that's causing the issue. This improves debugging experience and saves user some time if support isn't available at that moment.

Another reason to terminate automatically set actions is when a user is simply testing out new changes on their app and causes any API calls being accounted for and charged to the user

Potential solution

Provide a UI, like a button or a keyboard shortcut that opens up a terminate action modal making it easier for users to debug their app on their own
Edit the app in debugging mode so the user can paly around even on an app that's gone into a bad state (making changes, discarding changes on git for a git-connected app isn't the most elegant solution but is the current workaround for users)

Why should this be worked on?

A couple of scenarios when app goes into an unusable state and needs support to salvage it:

Infinite loop on custom code caused by a trigger field causing the app to hang and be inaccessible (sample app)
Using navigateTo() on the landing page causing a redirect each time user opens the app
Any other actions performed like copy, merge, duplicate that could cause the app to go into an error state

appsmithorg / appsmith