The application that arrived on time and was rejected

A training centre opened course applications through Microsoft Forms. A Power Automate flow reviewed each submission and rejected those sent before the opening date.

The creator had tested it several times during the day. It always worked.

Yet everyone who submitted between midnight and 01:00 on opening day received the same email: “Application rejected: submitted before applications opened.” From 01:00 onwards, the flow accepted them.

Why were applications from the first hour rejected?

How to solve the cases
A phone showing a submitted form next to a midnight alarm clock and a flow with two outcomes

Hints

Reveal them one at a time, only when you need them.

Solution

The flow compared the UTC date with the opening date in mainland Spain. During the first hour of opening day, it was still the previous day in UTC, so applications processed then were rejected.

What happened?

Cloud services commonly use Coordinated Universal Time (UTC). Microsoft documents that Power Automate uses UTC by default, and utcNow() returns the current UTC time. Mainland Spain is one hour ahead of UTC in winter and two in summer.

The flow used utcNow() at the point of evaluating the rule and compared only the date. In this case it processed submissions as soon as they arrived.

  1. Applications opened on 4 March. The rule accepted a request if its UTC processing date was on or after 2026-03-04.
  2. A request sent and processed at 00:20 on 4 March in mainland Spain was 23:20 on 3 March in UTC. The flow saw 2026-03-03 and rejected it.
  3. At 01:00 in mainland Spain, it was 00:00 UTC on 4 March. The dates now matched and the flow accepted the applications.
  4. Testing took place during business hours, when both dates matched.

In summer the two-hour difference would extend the fault until 02:00. It is easy to miss in tests because it occurs only when the local and UTC dates differ, just when people may be trying to apply first.

Technical explanation

The flow condition

As a Power Automate expression, the original comparison was equivalent to:

greaterOrEquals(
  formatDateTime(utcNow(), 'yyyy-MM-dd'),
  '2026-03-04'
)

Use the actual submission time and convert it to the time zone in which applications open. Here the previous step Submission_time_UTC contains the submission timestamp in UTC:

greaterOrEquals(
  formatDateTime(
    convertTimeZone(outputs('Submission_time_UTC'), 'UTC', 'Romance Standard Time'),
    'yyyy-MM-dd'
  ),
  '2026-03-04'
)

Romance Standard Time is the Windows time zone used for mainland Spain, Brussels, Copenhagen and Paris. It accounts for daylight saving time.

How could it be fixed and prevented?

To fix it, keep the actual submission time, convert it to the application’s time zone before comparing dates, and review rejected applications in order of arrival.

To prevent it from recurring:

  • Convert to local time for local date rules. Store the timestamp in UTC and use convertTimeZone() or the Convert time zone action to determine the local date.
  • Test around midnight. Try submissions just before and after midnight as well as during business hours.
  • Check run history. Power Automate records each run’s data. A trailing Z as in 2026-03-03T23:20:00Z denotes UTC.
  • Include the recorded date and time in the reply. A date from the previous day would have exposed the fault immediately.

Further reading

Power Automate’s UTC default and how to combine formatDateTime and convertTimeZone are covered in Customise or format date and time values in a flow — Microsoft Learn.

The time zone conversion action is described in Convert a time zone — Microsoft Learn.

The shared functions utcNow, convertTimeZone and greaterOrEquals are documented in Workflow expression functions reference — Microsoft Learn.

Windows lists Romance Standard Time for mainland Spain in Default Windows time zones — Microsoft Learn.

Have a story worth investigating?

Suggest a case

A project by Eniun

How do you solve the cases?

Each case presents a mystery that seems to defy explanation.

A moderator who knows the solution reads the mystery to the group. The group works out what happened by asking questions, discussing hypotheses and using what they know.

You can project the case on a screen so everyone can read it and refer back to it during the discussion.

The moderator can guide the discussion without giving away the answer. If the group gets stuck, each case offers three graded hints under “Hints”, which can be revealed one at a time.

Once the moderator confirms that the group has found the answer, select “Show answer” to open the solution.

You can also solve the cases on your own: read the story, try to come up with an explanation and use the hints only when you need them.