The Problem:

Currently, when a module is deleted, moved, or a developer's access permissions are removed, that module still appears in the "Recent Modules" left panel in Service Studio. When you inadvertently click on it, the platform tries to open it and throws an annoying error stating that you are not allowed to access the module (or that it doesn't exist).

This litters the recent items list with "dead links" and creates friction in the daily workflow.

Proposed Solution:

Service Studio should automatically refresh or validate the "Recent Modules" list. If a module is removed from the environment or if the user no longer has permissions to access it, it should immediately disappear from the recent modules panel.

Alternatively, clicking it could trigger a silent validation that removes the shortcut if the module is no longer accessible, instead of opening a dead end and throwing an error popup.

Benefits:

• Cleaner UI: Keeps the Service Studio workspace organized and relevant.

• Better UX: Prevents frustrating and useless error messages.

• Efficiency: Saves developers time by ensuring every click in the "Recent" panel actually leads to a valid module.