TimeZoneNotSupportedException

(0) Share

Report

Posted on by Hikari

Hi,

I have a flow that reads date from incoming mail and creates outlook.com tasks with a given due date.

Due date format is: 2018-06-04 02:00:00Z (YYYY-MM-DD)

However, recely (1-2 months) ago, create task step started throwing the following error:

"code": "TimeZoneNotSupportedException", "message": "A valid TimeZone value must be specified. The following TimeZone value is not supported: 'null'."

What time zone? How to set time zone for a task? Any ideas how to fix it?

Categories:

Building flows

I have the same question (0)

All responses (8)

Answers (0)

Sort by

v-yuazh-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @ Hikari,

Could you please share a screenshot of the configuration of your flow?

How would you get the Due date from the incoming mail?

The error message told that the Due date value is null,the null value is not supported.

Please check if the Due date value is null.

Please let me know if your problem could be solved.

Regards,
Alice Zhang

Was this reply helpful? Yes No
Hikari 14 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Thank you for your response. Here you have how it looks like (flow and create task step that ends up with the error):

Was this reply helpful? Yes No
Hikari 14 on at

Like (0)

Report
Copy link

Link copied!

Actually it looks like something has changed on MS Flow side a month ago as all my create outlook.com tasks started failing every time due to same error.

Any ideas how to fix it?

Was this reply helpful? Yes No
v-yuazh-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @ Hikari,

Could you please share more details about the body of the email or the screenshot of the email?

Could you please share more details about expression in the "Base Time" field of "Convert time zone" action?

I want to made a test on my said to recreate your scene to see what is the issue in your flow.

Also please check if it is because the datetime you get from the email body isn't a recognizable datetime so the flow would run fail.

Regards,
Alice Zhang

Was this reply helpful? Yes No
Hikari 14 on at

Like (0)

Report
Copy link

Link copied!

Hi,

So from mail I get the following string "2018-06-04" which mens 4th of June 2018.

Convert time zone was just a solution to the error that worked last month. However, it stopped working a few days ago (so this was the reason for my original post):

So it comes down to the question how to transform "2018-06-04" into a format that can be used as due date in create task step.

Regards

Was this reply helpful? Yes No
v-yuazh-msft Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hi @ Hikari,

I have made a test on my side,and don't have the issue that you mentioned.

The screenshot of my flow as below:

The flow would run successfully as below:

Please take a try to clear browser cache,recreate a new flow and made a test on you side to see if the issue still exists.

Please let me know if your problem could be solved.

Regards,
Alice Zhang

Was this reply helpful? Yes No
Hikari 14 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Thanks for help. Observation is actually interesting:
- if I follow you logic and create similar new flow it works fine
- if I do the same in my flow (I.e. input date via compose step having "2018-06-04" value then I get my error)
- I made sure that I get the same output from my substring code that extracts the above date from mail (also gives me "2018-06-04")

The easiest solution sees to be to create my flows from the scratch. Simple.

Any ideas what could have changed meantime that resulted in such strange situation?

Regards

Was this reply helpful? Yes No
GabrielStJohn Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hello, @Hikari!

Have you had a chance to apply @v-yuazh-msft‘s recommendation to adapt your Flow? If yes, and you find that solution to be satisfactory, please go ahead and click “Accept as Solution” so that this thread will be marked for other users to easily identify!

Thank you for being an active member of the Flow Community!

-Gabriel

Flow Community Manager

Was this reply helpful? Yes No