Action always shows the previously viewed record in the modal

Hello guys,

I’m experiencing an issue in our production application using Filament 3 + Livewire:

Error description:

When I click any Filament Action to view a record inside a modal, the component always shows the previously viewed record.
Only after performing a full browser refresh (F5) does it display the correct record.
On localhost everything works as expected.

Suspicions already ruled out:

Laravel cache: ran
```
php artisan cache:clear
```
php artisan cache:clear
```
php artisan cache:clear
```
php artisan cache:clear
,
```
config:clear
```
config:clear
```
config:clear
```
config:clear
,
```
route:clear
```
route:clear
```
route:clear
```
route:clear
,
```
view:clear
```
view:clear
```
view:clear
```
view:clear
and manually deleted
```
storage/framework/cache
```
storage/framework/cache
```
storage/framework/cache
```
storage/framework/cache
,
```
sessions
```
sessions
```
sessions
```
sessions
,
```
views
```
views
```
views
```
views
, and
```
bootstrap/cache
```
bootstrap/cache
```
bootstrap/cache
```
bootstrap/cache
.
Session driver: tested both
```
SESSION_DRIVER=file
```
SESSION_DRIVER=file
```
SESSION_DRIVER=file
```
SESSION_DRIVER=file
and
```
database
```
```
database
```
(with
```
sessions
```
sessions
```
sessions
```
sessions
table created via migration).
Environment parity: Filament 3, and Livewire versions/configs identical between local and production.
Browser cache: cleared cookies, tested in incognito mode and across different browsers.
JavaScript / Livewire: no console errors; Livewire and Filament scripts load without failure.
Filesystem permissions:
```
storage/
```
storage/
```
storage/
```
storage/
and
```
bootstrap/cache/
```
bootstrap/cache/
```
bootstrap/cache/
```
bootstrap/cache/
owned by
```
www-data:www-data
```
www-data:www-data
```
www-data:www-data
```
www-data:www-data
, perms
```
775
```
775
```
775
```
775
.

Current suspicion:
There seems to be a failure in state synchronization of the Livewire component used by Filament between AJAX requests. The session in production (especially with the

database

database

driver) or the authentication middleware may not be propagating the updated state, causing the component to “stick” to the previous record until a full page reload.

Thank you for any guidance or tips on specific logs/debugging techniques to capture component state across clicks.

Action always shows the previously viewed record in the modal

Similar Threads

Similar Threads

Similar Threads