An Azure service that automates the access and use of data across clouds without writing code.
Consumption Logic App missed first scheduled recurrence; checks began the following day
We have an Azure Consumption Logic App in West US 3 that emails a monthly cost report.
The schedule was configured in October for November 6, 2026,
at 09:00 UTC:
"recurrence": {
"frequency": "Day",
"interval": 1,
"timeZone": "UTC",
"startTime": "2026-11-06T09:00:00Z",
"schedule": {
"hours": [9],
"minutes": [0]
}
}
A trigger condition permits execution only on the 6th:
@equals(dayOfMonth(convertTimeZone(utcNow(), 'UTC',
parameters('schedule_time_zone'))), 6)
What we observed:
- No November 6 trigger entry or workflow run appears in history.
- Daily trigger checks appear starting November 7.
- November 7 shows Succeeded with Fired: False, as expected for the date condition.
- We found no enable, disable, or workflow update events around November 6.
- A manual run on November 17 successfully generated and emailed the report.
- The original date condition has been restored and published.
Microsoft documents that a daily recurrence configured less
than 24 hours before its start might skip the first occurrence.
Our schedule was configured weeks beforehand.
Is there a known interaction between a future startTime,
an explicit daily hour/minute schedule, and trigger conditions
that could explain this?
What additional diagnostics or configuration changes would
help establish the cause and prevent another missed occurrence?