Update Record in a Feature Layer - (silent) failure updating dates from epoch timestamp

[NigelCharmanPre-Prod]

Our flow includes an "Update Record in a Feature Layer" step. Since about 19:00 13 Feb UTC, this step has been consistently failing with the following error:

while updating with data like:

The date values have been retrieved from a different table using a "Get Data from a feature layer" step.

This flow has been working for months. It is running in NZST (UTC+13:00).

The main issue is this failing step.

A secondary issue is that the step appears to succeed, with an underlying HTTP return code of 200, so we only found out about the error from our users.

Keen for any thoughts on what may have caused this or what we could try to resolve it?

[DavidPike]

Might be worth trying a date string which the API should convert internally.  That would be the (possible) work around to get it working of-course, rather than an explanation.

"your_date" : "2025-02-01 09:00:00",
"or_maybe_this" : "2025-02-01T09:00:00",

[Rob32]

There's been a bug logged for this: BUG-000174431 - Creating a feature through Power Automate fails if a date is passed as an epoch value for a date field.

A workaround is to convert the epoch time to a DateTime string such as (2025-02-20T15:34:56.2424738Z) without the parentheses. The ArcGIS Connector "Convert date and time format" can also be used.

[NigelCharmanPre-Prod]

Thanks, this has now been fixed in the latest patch to the 2025.1 release.