FilamentPHP Livewire AJAX failures after mixed Vite asset manifests during rolling deployment

Resolution for Livewire AJAX Failures

Pinning the Admin Prefix

The recommended action is to pin the admin route prefix (e.g., /admin) to a single, stable deployment version until all active user sessions have naturally expired. This prevents the load balancer from serving HTML referencing a newer asset manifest while the client is still using assets from an older manifest.

Likely Explanation vs. Confirmed Facts

• Likely Explanation: During a rolling deployment, the load balancer may route subsequent requests for the admin panel to nodes serving a newer Vite build, while the client's active browser session is still referencing hashed asset URLs from an older build. This mismatch results in 404 errors for necessary Filament CSS/JS, breaking Livewire AJAX calls.
• Confirmed Fact: Filament v3 uses Vite manifests to inject versioned, hashed asset URLs into the HTML. Livewire AJAX relies on assets already loaded; it does not re-check the manifest during an in-session request.

Diagnostic Steps

1. Verify that the APP_KEY, session cookie domain, and session driver are identical across all nodes to rule out 419 CSRF errors as the root cause.
2. During cutover, inspect the browser's Network tab for 404 responses specifically on Filament CSS/JS assets when accessing /admin.
3. Compare the Vite manifest JSON files from the old and new builds, focusing on the hashed output paths for the primary Filament entry points (e.g., app.css, app.js) to confirm hash drift.

Missing Diagnostic Detail

To refine the recommendation, confirm whether your load balancer enforces session stickiness for the /admin path.