Support the ongoing development of →
posted 2 years ago
Last updated 2 years ago.


This is intended, the callAfterCallbacks method is not inside the Event class, it's inside the ScheduleFinishedCommand class ( if I'm not mistaken.

By having a closer look at the buildBackgroundCommand method inside the CommandBuilder class (, you can see that the schedule:finish command is executed after the command itself has been executed.

So a few possible situations I can think of:

  • the intended command doesn't execute properly
  • the intended command returns a non-zero exit code
  • the intended command throws an exception which also quits everything after it
  • there's a problem with the path to your binary
  • there's a problem with the (execution/access) rights of your binary
  • there's a problem with the path to the finish command (possibly non globally reachable php binary or other binaries that are needed, ...)
  • running your binary results in a timeout which itself aborts everything after it

Sign in to participate in this thread!


Your banner here too?


We'd like to thank these amazing companies for supporting us

Your logo here?

The Laravel portal for problem solving, knowledge sharing and community building.

© 2024 - All rights reserved.