have you checked (written to log) what exact date pause should wait until?

is dateRequiredReminder variable always populated?

Not sure what u mean by if it is populated.

that is pretty much what sets the daterquiredReminder and a basic wait until that variable is met.

in mean time all other requests are using the same workflow ...

check written to log !?

not sure about this one :/

Not sure what u mean by if it is populated.

if it is not empty for any reason.

check written to log !?

have a look on 'Log in history list' action

Hi ‌

Yes from what I can see there is a log in the workflow task history.

It records when to pause it until ... but then does not imitate on that date.

As already mentioned, the WF works in general pretty good apart from them two occassions.

To safe the hassle of terminating the workflow and re-run it with an updated wf > I have disabled the wait until for now.

Saying this, wonder what process can be implemented so when a WF fails at a particular point > how do I configure it so the current running process refreshes and re-runs from the same spot again???

you have said above "The workflow occasionally stops at Pause Until"?

what that exactly mean - what's the workflow status?

how much time have you waited after pause until deadline?

have you checked timer job service whether it doesn't experience any problems?

Yes, true ... so far it happened twice and I disabled the Pause Until function to avoid the hassle.

The status remains "in process / running" and actually they are still running and will have to terminate the process.

As a workaround, I had to upload a new WF which continues just after the pause function to complete the process. This also means the initial running process has to be terminated / stopped > which in return sends an email to the user about the request being cancelled / stopped < this is not ideal.

how long I waited??

The calculated function takes -7 from the request date eg. 7/11/2017 becomes 31/10/2017 stored as dateRequiredReminder which is supposed to be triggered. I waited until 1 day before the request date in hope the process will start but no luck ...

have you checked timer job service whether it doesn't experience any problems?

I don't have access to the SP Admin side.
I have asked the relevant group to look into this matter but no response since.

I thought maybe my wf is not set up properly.

as far as I can say, I don't see a problem with your configuration.

I suspect either there is a problem with your infrastructure and workflow is not restarted after the pause elapses, or there might be a bug in pause implementation on 2016.