This Customer Journey uses a Segment with a different time zone.

(0) Share

Report

Posted on by Community Member

Good morning all.

For a while now, I've been using Dynamics CRM for Marketing. I've created a lot of Marketing E-mails with no issues whatsoever; But on the 3rd of February all of my Customer Journeys have errors saying that "This Customer Journey uses a Segment with a different time zone."

I have checked my settings and the Time Zones on the Journey and the System are the same (GMT)

I'm having trouble fixing this, and would be very happy if someone could walkthrough me on this issue.

Best Regards, and hoping a fast response,

Emanuel Maia

I have the same question (0)

All responses (8)

Answers (1)

cloflyMao 25,210 on at

Like (0)

Report

Hi Emanuel,

Can you still publish the customer journey successfully(in Live status) regardless of the warning?

(or run a new simple customer journey successfully)

Regards,

Clofly

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Good morning Clofy.

I just tested it and though the error still appears, the e-mail goes through.

Yesterday it didn’t work but today it’s working.

What about the error though? Will it always be here for the next Costumer Journeys?

Was this reply helpful? Yes No
Verified answer

cloflyMao 25,210 on at

Like (0)

Report

Hi Emanuel,

I also encountered this issue in my current environment.

After I've enabled 2020 wave 1 release update for my marketing application, I found that a new field "Time Zone" is available for static segment:

The description of the field said that its effective time zone for this segment.

However, I didn't find more details about how this field actually works from published doc:

https://docs.microsoft.com/en-us/dynamics365-release-plan/2020wave1/dynamics365-marketing/

So I think there would be some new feature that is under testing on back-end.

Due to e-maill could still go through, you could wait for some days to see whether the warning would disappear.

Regards,

Clofly

Was this reply helpful? Yes No
Petit Hibou on at

Like (0)

Report

Hi Emanuel!

are you on the February release/early access version?

The issue might relate to the new feature related to timezone aware segments. This one is addressing the situation when customer journeys are time zone-specific (user explicitly specifies time zone in the UI), while segments are evaluated in the context of UTC (eg if you use "Today" operator in dynamic segment's filter)

I'd be interested to learn more about your experience and find out if any correction required from engineering side. Can you please write me on eosipova@microsoft.com, so that we can arrange a confcall?

Br

Elena

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Clofy.

The version we are currently using is "2019 edition 2".

I have talked to the IT Department and we will upgrade our CRM to the new Version soon.

In the meantime we activated CRM Sandbox in order to conduct further tests on different areas.

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

Hello Elena, thanks so much for the reply!

As i said on my last post, we are currently running "2019 edition 2" and will upgrade to the latest version very soon. Work is being made as we speak to re-enable our Sandbox so we can conduct further testing on different matters.

We will definetly send you an e-mail with more contact details.

Thanks again for the response!

Was this reply helpful? Yes No
dfgdhsjjffj 35 on at

Like (0)

Report

I'm using dynamic segments with no time related parameters and am also getting the warning: segment is in a different time zone than the journey

Was this reply helpful? Yes No
Suggested answer

Petit Hibou on at

Like (0)

Report

Hi KR,

in March release we're removing the warning for segments where timezone was not filled in or those that were created on the old version (where timezone can't be set up) . Please check it when you have the March release and let me know if it works well

Br

Elena

Was this reply helpful? Yes No