Test activity - time condition not working correctly

[FilipFiebiger]

Hello everyone!
I'm using below as a condition in my test activity:
Hour(GetDate())>13
Does anyone have any idea why this condition doesn't work correctly?
I checked and when for example using enrichment with this function and I can see the data is populated correctly.
But for some reason this test is giving me wrong results. I'm extremely confused about it, it this some Adobe bug?

[tapcxm_josh]

Hi @FilipFiebiger ,

Just tested this in our sandbox instance and it worked as expected for me (current time 4pm here):

What time (+time zone) did you run your test and what time zone is your ACS server time in?

Thanks,

Josh

[_abhishek_]

@tapcxm_josh,

I was also facing same issue. If you try with few more conditions and try reversing the conditions, you will get to know what @FilipFiebiger is trying to explain. If you try Hour(GetDate())>13 and Hour(GetDate())<13 you will get two different answers. I guess, there is some issue with the Test activity.

For the workaround, we can use Segmentation activity to meet the requirement.

[FilipFiebiger]

@tapcxm_joshthanks for replying!
Since writing the post I investigated the issue further and it turned out that the time for test activity is different than time for other blocks.

So for example Hour(getDate()) executed in enrichment gives 13 and the same expressions Hour(getDate()) executed in test gives 11.
It is now with Adobe support, they suspect it's discrepancy between application and database server... It is extremely frustrating how such a bug can happen?
Where can I find my server time zone for Adobe Campaign Standard?
PS. I know your reply isn't correct answer but I miss clicked and can't change it

[Sukrity_Wadhwa]

Hi @tapcxm_josh,

Can you help @FilipFiebiger further here? 

Thanks!

[FilipFiebiger · Accepted solution]

The problem is that Test and Query are using different time zones and Adobe Engineering Team is not able to make them in alignment. So it seems on some clients they are misaligned, and If you have that issue as me they will not correct it - that's the answer I got after a month of back and forth with support. Great job Adobe!
The workaround is to set time zones manually in both blocks then it should give proper results.