I have a question regarding a stalled state machine, i have looked through the forums and the advise against stalled state machine but i cant seem to find a solution.
The workflow stalls when it tries to move onto the Business Data Architect which has a person designated in it to send the item to. The person listed is me and works through all the other stages. The workflow says it is active but then just sits there after the Change state section. Does anyone have any ideas what i might be doing wrong?
I have attached the workflow as it is at present.
Thankyou for the repsonse. where would you recommend the Commit pending changes action to go? Would you place it at the end of the state where it isnt working or at the beginning of the next one? Havent used them before so unsure where to place it
In the Run If box there is a condition:
condition :if current item field equals value
Where: Status / equals / Value / Local cost centre owner approver
This the previous stage and the item is updating and emailing out that the local cost centre has been approved, it seesm to go through the run if but then gets stuck at the change state stage
Does the SharePoint farm have multiple servers? We experienced the same problem with some of our customers with multi-server farms.
In these cases, the problems seems to occur due to a caching problem.
You can check this by opening the cache.ini file on each server (located in C:\ProgramData\Microsoft\SharePoint\Config) and comparing the number in the file.
If the numbers are different, there is a problem with the cache.
To fix it you can do the following:
If the problem is with the cache, this will fix it.
Hope it helps,
In this kind of a workflow it looks like you need to put Commit Pending Changes before you change state, in that way you are committing all the changes before you move to the next state.
I have tried this on mine and it did help I have another issue but this specific one has been resolved by committing my change before changing state.