Hello, I got the same issue. Not sure if it will be the same for you guys but it appeared in my case on payments. So this problem appears if the context doesn't have an employee in its parameters, and it comes from SymfonyContainer since it tries to call ps core api stock movement repository, and the context is made out of scope so it doesn't have an employee. In my case, I found a module witch initiates a new AppKernel which is requered for Symfony(dont know all the details but if it's called in front it creates symfony container) to work and it caused a problem. A recommendation is to try to find a module witch is trying to call a new Kernel and boot it. If you don't have access to code, it's not much you can do just try disabling custom modules.
Edit History
Hello, I got the same issue. Not sure if it will be the same for you guys but it appeared in my case on payments. So this problem appears if the context doesn't have an employee in its parameters, and it comes from SymfonyContainer since it tries to call ps core api stock movement repository, and the context is made out of scope so it doesn't have an employee. In my case, I found a module witch initiates a new AppKernel which is requered for Symfony(dont know all the details but if it's call in front it created symfony container) to work and it caused a problem. A recommendation is to try to find a module witch is trying to call a new Kernel and boot it. If you don't have access to code, it's not much you can do just try disabling custom modules.
Hello, I got the same issue. Not sure if it will be the same for you guys but it appeared in my case on payments. So this problem appears if the context doesn't have an employee in its parameters, and it comes from SymfonyContainer since it tries to call ps core api stock movement repository, and the context is made out of scope so it doesn't have an employee. In my case, I found a module witch initiates a new AppKernel which is requered for Symfony(dont know all the details but if it's call in front it created symfony container) to work and it caused a problem. A recommendation is to try to find a module witch is trying to call a new Kernel and boot it. If you don't have access to code, it's not much you can do just try disabling modules custom modules.
Hello, I got the same issue. Not sure if it will be the same for you guys but it appeared in my case on payments. So this problem appears if the context doesn't have an employee in its parameters, and it comes from SymfonyContainer since it tries to call ps core api stock movement repository, and the context is made out of scope so it doesn't have an employee. In my case, I found a module witch initiates a new AppKernel which is requered for Symfony(dont know all the details but if it's call in front it created symfony container) to work and it caused a problem. A recommendation is to try to find a module witch is trying to call a new Kernel and boot it. You you don't have access to code, it's not much you can do just try disabling modules custom modules.