Request abort behavior during long-running Filament Actions

Direct Answer

No, Filament v3 does not provide a built-in mechanism to detect a Livewire disconnection within a synchronous Action to stop execution. Because PHP is a share-nothing architecture, once the server begins processing the request, it will continue until the logic completes or a system timeout (like max_execution_time) is reached, regardless of whether the client has closed the browser.

Similarly, there is no documented, standardized UI mechanism in Filament to trigger the cancellation of a job already dispatched to the queue. Queue cancellation must be implemented manually via application state.

Synchronous Action Behavior

When a user triggers a Filament Action, the request is handled by the web server (e.g., Nginx/Apache) and passed to PHP-FPM. If the user navigates away, the TCP connection is severed, but the PHP process remains active.

Detection Limitations

While PHP provides connection_aborted(), it is often unreliable in modern environments because:

• It typically only updates when PHP attempts to send output to the client.
• Output buffering (common in Laravel/Livewire) may hide the disconnection from the script until the buffer is flushed.

Implementing Cancellation for Queued Actions

Since Filament cannot natively "stop" a running worker process, you must implement a cooperative cancellation pattern. The job must periodically check if it should continue.

Recommended Implementation Steps

1. Store the Job ID: When dispatching the job from the Action, store the Job ID in your database associated with the record or user.
2. Create a Cancellation Flag: Implement a separate Filament Action (e.g., a "Cancel Process" button) that sets a flag in the cache or database (e.g., cache()->put("cancel_job_{$jobId}", true)).
3. Poll for Cancellation: Inside the handle() method of your queued job, check this flag during long loops:

   foreach ($items as $item) {
           if (cache()->has("cancel_job_{$this->jobId}")) {
               return; // Exit gracefully
           }
           // Process item
       }

Verification and Assumptions

These behaviors assume a standard Filament v3 installation running on a traditional PHP-FPM/Nginx stack. If you are using an asynchronous runtime like Laravel Octane (Swoole/RoadRunner), request termination behavior may differ, though the lack of a framework-level cancellation token remains.

To verify your specific environment: Create an action with a sleep(30) and a log entry at the end. Trigger the action, close the browser immediately, and check your logs to confirm the process finishes despite the disconnect.