web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Date/Time from SharePo...
Power Automate
Unanswered

Date/Time from SharePoint list "error"

(0) ShareShare
ReportReport
Posted on by 65

Greetings,

 

I am connecting a flow to a SharePoint list with a field I labled "FollowUp" it is a calculated field based an entered End Date.

 

For testing purposes, I am trying to add a few minutes =End+1/24/30, when this date is used a flow delay until, I get this error. Is there a conversion I should be doing? (I want a followup email to be sent 2 days after the scheduled "End" Date.

 

BadRequest. The 'timestamp' value of the 'Wait' action 'until' inputs must be specified in UTC using the round-trip date/time pattern (for example, '2015-10-22T10:00:00Z'). For details please review the Standard Date and Time Format Strings of the .Net framework.

 

Regards

Categories:
I have the same question (0)
  • v-yamao-msft Profile Picture
    Microsoft Employee on at

    Hi fklatecki,

     

    Per my certain knowledge, SharePoint Calculated column will return a Text value, while you are trying to use Date/Time value.

     

    Please consider to use Workflow Definition language adddays function in your flow:
    https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-workflow-definition-language

     

    You could use a adddays function in a Compose action in your flow looks like below:

    3.PNG

     

    Please feel free if you need more help.

     

     

    Best regards,
    Mabel Mao

  • fklatecki Profile Picture
    65 on at

    Thank you for offer to assist. I am not sure if I am using the adddays function correctly. For testing purposes, I am using addseconds to make my testing faster.

     

    I am getting this error message in the flow:

     

    InvalidTemplate. Unable to process template language expressions in action 'Delay_until' inputs at line '1' and column '2049': 'The string was not recognized as a valid DateTime. There is an unknown word starting at index 0.'.

     

    image 1.pngimage 2.pngimage 3.pngimage 4.png

  • v-yamao-msft Profile Picture
    Microsoft Employee on at

    Hi fklatecki,

     

    I would suggest you use Compose action likes I mentioned before and use the Workflow definition language adddays. Then select the dynamic content of Compose action for Delay until field.

     

    Please try it and feel free reply if you need more help.

     

    Best regards,
    Mabel Mao

  • MWilliams86 Profile Picture
    Microsoft Employee on at

    The way I got around this was that I had a SharePoint column that took in a Date Only, used the Dynamic Content selector for it and added the Time format requested by the delay of T00:00:00Z. It looks like this:

     

    Flow Forum Capture.PNG

     

    This processed fine it seems. Feel free to use the 24 hour format on the time to adjust when you'd like the delay for. For the actual addition process you may want to try and get the more advanced @adddays() function to work, but this should fix the initial issue/error you were receiving. 

  • fklatecki Profile Picture
    65 on at

    Thank you for the additional information. Unfortunately, I am still get a TimeStamp error.

     

    As you can see the calculated SharePoint column is Date Only. I do send an email from the Flow, and use the Follow Up date field. As you see in the Outlook email the Date field is Universal Time, not withstanding the column is "Date Only".

     

    I would appreciate any further advise you may have to offer.

     

     

     

    flow time error_Page_1.jpgflow time error_Page_3.jpgemail fields.pngDelay error.pngDelay until.png

  • kenleung Profile Picture
    16 on at

    I just got this to work. I had to change the format of my field from Date Only to Date & Time. For some reason, Flow's "Delay Until" action hates date only fields. Even more of a pain since I'm using an InfoPath form template for the list. I hate these stupid pointless gotchas.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Automate

#1
David_MA Profile Picture

David_MA 251 Super User 2026 Season 1

#2
Haque Profile Picture

Haque 239

#3
Expiscornovus Profile Picture

Expiscornovus 220 Most Valuable Professional

Last 30 days Overall leaderboard