We’re getting hundreds of these warnings in the PSO Events view log every day. Any idea what config/conflict is causing this? We’re using FSM as the EA to PSO.
![](https://uploads-eu-west-1.insided.com/ifs-en/attachment/2051b9ee-e82b-4a85-9da7-8a1d5a243574.png)
We’re getting hundreds of these warnings in the PSO Events view log every day. Any idea what config/conflict is causing this? We’re using FSM as the EA to PSO.
Hi
Can you confirm whether the load file contains overlapping shifts or not. If it does, then you will need to investigate how this may have happened.
Any questions let me know,
Thanks,
Kai
Thanks, kai.parker, for your reply. We use ARP for shift creation. There have been some issues with FSM DB locks and it seems FSM and PSO sometimes get out of synch. Updating statuses in FSM and clearing any outstanding historical activities in PSO ARP seemed to resolve the problem. Your reply is appreciated.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.