Skip to main content

Hi,

I have an issue and it seems I can't find a general solution.

I need to report some timestamps regarding Workflow Tasks for specific workflows. After each Task, using the Task ID I query the Workflow Task list and save the Created and Modified dates into variables. If I write these variables then into WF history log, the date is correct.

But after that I want to create a new Item into a "Report" list in which I store this dates too from the variables. For some reason in the list teh created Item's value is 2 hours more then it was in the variable...

I use this action at least 50 places across multiple workflows... 

Server times are correct.

We are in UTC+2, Time Zone, maybe that's the key but I don't know how to modify easily, without changing everywhere the workflows.

Any idea?

Thanks in advance!

Robert

Maybe something to do with Sharepoint site regional settings : check if Time Zone and Regional Settings are correct.

For example if you set TimeZone to UTC+2 but set Locale to Japan, this could cause some issues.


Unfortunately, that's correctly configures. This was my first idea too, then server time...


Hello Szabó Róbert​ -

This may not be the best solution, but for the now, what about doing a calculation and subtracting 2 hours? If this is the case for ALL ITEMS, this may get you through until it is resolved.


Thanks, I had the same idea of workaround, but I have to change it then in 100+ places across multiple workflows. Of course I can do it, but the issue itself bothers me in general...


I am having the same issue. In the workflow the value is correct but when it goes to update the list it is subtracting 4 hours from the time making it UTC+-0.


Well, I couldn't solve the mystery. If you find anything please share. happy.png Good luck!


I am running 3.5.1 nintex said it was fixed in 3.6.1 what version are running


We have 3.5.1 too, I think we installed last September, since then I couldn't dare to upgrade grin.png


We have had the same issue with a few farms. I would recommend using a global UDA for such calculations, in that case you could change the date calculation easily across the whole farm if the need should arise.


Hi Martin, 

Thank you and I understand, but my issue was not about calculations but simply "saving time-stamps". Using UDA for every field update (20-30x) is a bit too much for me. It's only 1 WF for me and I'm over this, I can live with that. 


We're having the same issue.... except that we r in time zone UTC +3 


Did anyone of you manage to find a solution for that?


I am having the same issue in a workflow.


 


When the item is created, two hours are added automatically and sent to the requester in a notification. This causes some confusion to endusers.


Reply