Forum Discussion
Solved
Weird problems saving to a list
We have a weird problem where when users save updates to a list their screen takes 45-60 seconds to refresh after they hit the save button. The weird thing is that the data is saved almost immediate...
- I'll reply to my own question in case anyone else has a similar problem.
The issue was that at some point in the past there had been a 2013 workflow that was added to this list. That put an event reciever on the list that was still there, even though the workflow was gone.
On the workflow manager server we ran the GetWFFarmStatus and Get-SBFarmStatus commands, and that showed us that the services were not running.
The fun part about this was that if you just looked in the Services list it showed them as running. But if you clicked on them the only option was to Start them, even though the status showed them as running. Once we clicked start on them everything worked properly.
I'll reply to my own question in case anyone else has a similar problem.
The issue was that at some point in the past there had been a 2013 workflow that was added to this list. That put an event reciever on the list that was still there, even though the workflow was gone.
On the workflow manager server we ran the GetWFFarmStatus and Get-SBFarmStatus commands, and that showed us that the services were not running.
The fun part about this was that if you just looked in the Services list it showed them as running. But if you clicked on them the only option was to Start them, even though the status showed them as running. Once we clicked start on them everything worked properly.
The issue was that at some point in the past there had been a 2013 workflow that was added to this list. That put an event reciever on the list that was still there, even though the workflow was gone.
On the workflow manager server we ran the GetWFFarmStatus and Get-SBFarmStatus commands, and that showed us that the services were not running.
The fun part about this was that if you just looked in the Services list it showed them as running. But if you clicked on them the only option was to Start them, even though the status showed them as running. Once we clicked start on them everything worked properly.