Hello @Makoto Oda ,

Thanks for the question and using MS Q&A platform.

My understanding is that when you are using Tokyo Standard Time in convertFromUtc function in additional columns of your source, while doing data previw you are seeing errors mentioned above. So, to work around, you have changed Tokyo Standard Time to Asia/Tokyo and the data preview worked fine. And when you debug run the pipeline it failed with error mentioned above. So then you have again changed it back to Tokyo Standard Time from Asia/Tokyo and then the debug run was successful. So, you would like to understand what the correct behavior is. Please correct if my understanding is incorrect.

In order to validate the feedback, I tried to reproduce the issue on my end using the same dynamic expression you have provided above - @formatDateTime(convertFromUtc(utcNow(), 'Tokyo Standard Time'), 'yyyy-MM-dd HH:mm:ss.fffffff') and tried to preview the data, unlike your scenario the preview data was successful without any issues. I also did data preview in mapping
section and the preview were successful here too. Please see below GIF for additional justification.

Hence, my pipeline source data preview was successful for Time Zone Tokyo Standard Time .

I also tried using Asia/Toky in dynamic expression, but the data preview is failing with error the value provided for the time zone id 'Asia/Tokyo' was not valid

My understanding from these tests is that Tokyo Standard Time is correct one to use and it should work as expected when you do preview data or debug run pipeline. But if you are able to reproduce the issue consistently on your end, then I would recommend filing a support ticket for deeper analysis as we weren't able to reproduce the issue on our end.

Additional info :
While working on the issue, I noticed that you are using formatDateTime() function to convert the format. You can avoid using that additional function as you can specify the format type in convertFromUtc() itself. For more info, please refer to this documentation - ADF control flow expression language functions#convertFromUtc

Hope this info helps. Please let us know if any further queries.

------------------------------

Please don't forget to click on or upvote button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer. Here is how

@KranthiPakala-MSFT Thank you for your elaborative checking and answer. Your understanding is perfectly correct. Thank you for additional info about convertFromUtc function's parameter too. I fixed it.

I don't know that this issue is related, the background operating system in the 'preview' has an effect on this problem?

According to Azure Functions' Document , Asia Tokyo Standard seems to be Windows' format and Asia/Tokyo seems to be Linux's format.

I use a Self-hosted integration runtime of Windows OS.

I think that in my environment, the background operating system in the preview is Linux.
However, it is possible that the background operating system vary from subscription, region.etc?

Hello @Makoto Oda ,

Thanks for your response. I doubt anything to do with your background operation system with regards to this issue except SHIR as it has to be installed only in Windows machine.

But could you please confirm if you are able to reproduce the issue consistently? If yes, then could you please share your data factory region, so that I will try to analyze around it.

If the issue is not able to reproduce, then it will be hard to analyze and provide justification about this behavior, and you may have to file a support ticket so that they can involve relevant product owners to further have a look.

Thank you

@KranthiPakala-MSFT

Thank you for your reply. The issue still occurs. My region is Japan East.

Could you analyze, please?