Timezone problemsf

Avatar

Avatar
Ignite 1
Level 2
szymons55769873
Level 2

Likes

5 likes

Total Posts

22 posts

Correct reply

0 solutions
Top badges earned
Ignite 1
Validate 1
Give Back
Boost 5
Boost 3
View profile

Avatar
Ignite 1
Level 2
szymons55769873
Level 2

Likes

5 likes

Total Posts

22 posts

Correct reply

0 solutions
Top badges earned
Ignite 1
Validate 1
Give Back
Boost 5
Boost 3
View profile
szymons55769873
Level 2

09-07-2019

Hello

I'm trying to run a workflow based on an option that stores the last run of the workflow.

I'm querying the Recipient tracking logs for "logDate" and comparing that with the option as "on on after"

I have a delivery that has its tracking logs all on 8:ish, so 8:05, 8:30 and 8:55.

The option is, double confirmed in the workflow log, set at "Mon Jul 08 2019 09:28:53 GMT+0100 (BST)".

When I run the query then, it should not find any records because 8:05, 8:30 and 8:55 are not 'on or after' Mon Jul 08 2019 09:28:53 GMT+0100 (BST).

However when run, it shows one record, the one from 8:55.

How is that possible?

ps. The server time is set on Europe/London Timezone, so BST as well.

what am I doing wrong?

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Establish
MVP
wodnicki
MVP

Likes

977 likes

Total Posts

1,096 posts

Correct reply

516 solutions
Top badges earned
Establish
Affirm 500
Contributor
Shape 1
Give Back 100
View profile

Avatar
Establish
MVP
wodnicki
MVP

Likes

977 likes

Total Posts

1,096 posts

Correct reply

516 solutions
Top badges earned
Establish
Affirm 500
Contributor
Shape 1
Give Back 100
View profile
wodnicki
MVP

11-07-2019

Hi,

Check that server timezone (logInfo(execCommand('date') in linux) and db timezone (xtk:option wdbctimezone) match.

There are also workflow timezones and operator timezones. If they're not all the same, make them the same.

Thanks,

-Jon

Answers (0)