Long Running Process Visible After closing Browser

Feature Request: Long-Running Process Visibility After Browser Closure

Summary:
Enable users to view and track long-running processes even after they close their browser. The feature should preserve visibility into the status of background operations so users can confirm whether a process is still running, completed successfully, or failed without needing to keep the original browser session open.

Problem Statement:
Currently, if a user starts a long-running process and then closes their browser, they lose visibility into that process. This creates uncertainty about whether the operation is still in progress, completed, or encountered an error. As a result, users may repeat actions unnecessarily, waste time checking manually, or lose confidence in the system’s reliability for handling lengthy background tasks.

Proposed Solution:
Provide a persistent way for users to view the status of long-running processes independent of the active browser session.
Track background processes on the server side and make their current state available when the user returns to the application.
Display key process details such as start time, current status, completion state, and any relevant error messages.
Ensure users can easily access a list or history of recent long-running processes after signing back in or reopening the browser.
Prevent duplicate process execution by clearly indicating when an identical process is already running or has recently completed.

Benefits:
Improves transparency and trust by allowing users to confirm the outcome of long-running operations.
Reduces duplicate submissions caused by uncertainty after a browser is closed.
Saves time by eliminating the need for manual follow-up or repeated attempts.
Creates a more reliable and user-friendly experience for workflows involving background processing.