Level 31
Is there something in storage/logs/laravel.log at the moment of 500 error?
Jul 15, 2025
8
Level 1
Filament notification 500 error
I am working with Filament v3 and Laravel v12. Whenever a Filament notification is created, it throws 500 error and stop the project. Even if I try to run the project again, it will still throw the 500 error. Only after I clear the sessions table or generate a new app_key, the project run again. This happens when I submit any form and filament try to create "Successfully" notification or when I manually try to create filament notification "Notification:make()".
Below are the things that I tried but didn't work:
- changing SESSION_DRIVER to 'file'.
- clearing cache or config
- running composer install or update
Level 1
@Glukinho There is this error message and I already tried increasing memory_limit on php.ini. And I don't think there is any recursive or infinite loop function happening either because it was working at first and when I run composer update it starting happening like this. I also tried making a new filament project and it also happens in the new project:
Allowed memory size of 536870912 bytes exhausted (tried to allocate 131072 bytes) {"userId":1,"exception":"[object] (Symfony\Component\ErrorHandler\Error\FatalError(code: 0): Allowed memory size of 536870912 bytes exhausted (tried to allocate 131072 bytes) at D:\Projects\web-apps\top-up-nation\storage\framework\views\1bb57ddc19d401c27a42741ae2b78db6.php:394)
Level 31
@Danielzct what is in file D:\Projects\web-apps\top-up-nation\storage\framework\views\1bb57ddc19d401c27a42741ae2b78db6.phpat row 394?
Level 1
@Glukinho it's just a close 'a' tag ''
Level 31
@Danielzct show your code? A method which causes mmeory error at least.
Level 1
@Glukinho I have found the solution. The problem was with a change introduced in Laravel 12 which leads to an infinite loop. I solve it by updating filament to the current latest stable version 3.3.31. Thank you for your time.
1 like
Level 31
@Danielzct thanks for sharing, it seems to apply to my case as well.
Level 1
@Danielzct You're such a life saver!! I spent a week trying to resolve the same issue. I finally resolved it with your solution!
Please or to participate in this conversation.