using utcNow() results in "Location Service must be enabled to run this flow" message

(0) Share

Report

Posted on by MelissaReed

292

I have an instant (manual) flow that runs great until I use the function utcNow() to get the current date/time.

This only started happening a day or two ago. I've used utcNow() successfully for years. Initially it seemed to only occur in one specific env, but now I get the error in all environments.

Also once I delete the Action that calls utcNow(), the error persists. I have to delete the trigger action and recreate it, then it runs fine. Until I call utcNow() again.

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

fchopo 8,003 Moderator on at

Like (0)

Report

Hi @MelissaReed

In which action are you using the expression? I just did a test on my tenant (located in Europe) and is working fine (using utcNow() in a "Compose" action).

Probably the error is related to using the Location trigger. Please be sure to set the status of the Location to On, then re-run Flow to see if the problem exists:

Regards,

Ferran

Was this reply helpful? Yes No
MelissaReed 292 on at

Like (0)

Report

I'm marking this as solved though I personally ran into a wall -- Location Services is blocked by the desktop administrator. Working to get an exception on that.

What I don't understand is why there isn't the ability to fetch current datetime without requiring Location Services. I get that it's probably because it wants to know my time zone and that's convenient but those of us without the ability to turn on Location Services are stuck. Is there such a function I could use as a workaround?

Was this reply helpful? Yes No
LP-16090700-0 2 on at

Like (0)

Report

Did you find any solution in the end? I am getting the same issue as my org also block Location Services.

Was this reply helpful? Yes No