Process automation API trigger fails to start scheduled flow

BPM Microsoft Power Platform
, , , , , , , ,
1

We’re experiencing issues with scheduled flows in our process automation setup. The API trigger we’ve configured to start flows at specific times is consistently failing or missing executions.

The flow is supposed to run daily at 6 AM EST to process overnight orders, but it’s been skipping runs randomly. When I check the API logs, I see the trigger request hitting the endpoint, but the flow doesn’t start. Here’s the trigger configuration we’re using:

{
  "recurrence": {"frequency": "Day", "interval": 1},
  "startTime": "2025-01-01T06:00:00Z",
  "timeZone": "Eastern Standard Time"
}

The strange part is that manual triggers work perfectly fine. We’ve also noticed the issue seems worse around the time daylight saving would have transitioned. Has anyone dealt with DST handling problems in Power Platform’s process automation API? We’re on the 2024 Wave 2 release and this is affecting our order processing workflow significantly.

2

That’s interesting. So you’re saying the startTime should always be UTC format regardless of the timeZone setting? I assumed the timeZone parameter would handle the conversion automatically. That might explain the inconsistent behavior we’re seeing.

3

I’ve seen similar behavior with scheduled triggers. First thing to check: are you using UTC in your actual API calls but EST in the configuration? The Power Platform process automation API expects UTC timestamps in the startTime field, even when you specify a timeZone parameter. The timeZone is used for recurrence calculation, not the initial timestamp interpretation.

4

Based on the symptoms you’ve described, you’re dealing with a combination of three issues that need to be addressed systematically:

1. Time Zone Configuration: Your startTime must be in UTC format, not local time. Convert your 6 AM EST to UTC (11:00:00Z) in the API call:

{
  "recurrence": {"frequency": "Day", "interval": 1},
  "startTime": "2025-01-01T11:00:00Z",
  "timeZone": "Eastern Standard Time"
}

2. DST Handling: The Power Platform API doesn’t automatically adjust scheduled triggers for DST transitions. You have two options:

  • Use UTC consistently and handle time conversion in your application layer
  • Implement a DST-aware scheduling service that updates trigger configurations when DST changes occur (typically twice a year)

For production systems, I recommend the UTC approach. Create a helper function that converts your desired local time to UTC before making API calls.

3. Scheduled Flow Trigger Reliability: The ‘Skipped’ runs you’re seeing indicate concurrency conflicts. Update your flow settings:

"concurrency": {
  "runs": 1,
  "maximumWaitingRuns": 10
}

This ensures that if a run is in progress when the next trigger fires, the new run waits in queue rather than being skipped.

Additional Recommendations:

  • Enable detailed logging in your flow to capture trigger timestamp information
  • Set up Azure Application Insights integration to monitor trigger patterns
  • Implement health check flows that validate scheduling accuracy
  • Review your API authentication token expiration settings - tokens should be valid for at least 24 hours beyond your scheduled run time

After making these changes, monitor your flow history for 3-4 days to confirm consistent execution. The combination of proper UTC handling, concurrency configuration, and DST awareness should resolve your missed automation issues. If problems persist after implementing these fixes, check the Power Platform service health dashboard for any regional issues affecting scheduled triggers.

5

Checked the flow history and found something interesting. The flows that are ‘missing’ are actually showing as ‘Skipped’ in the history with a reason of ‘Trigger condition not met’. But we don’t have any trigger conditions configured. Could this be related to the timezone/DST issue causing some kind of internal condition evaluation to fail?

6

I ran into this exact issue last quarter. The problem gets worse with DST because the API doesn’t automatically adjust scheduled triggers when the clock changes. You need to explicitly handle DST transitions in your trigger configuration. We ended up implementing a monitoring service that checks if flows are executing as expected and reconfigures triggers after DST changes. Also, make sure your connection refresh tokens aren’t expiring - that can cause silent failures where the trigger fires but lacks authentication to start the flow.

7

Adding to what others mentioned - check your flow’s run history in the Power Automate portal, not just the API logs. Sometimes the trigger fires correctly but the flow itself has a configuration issue that prevents execution. Look for any conditional logic at the start of your flow that might be evaluating to false. Also verify that the service account or app registration you’re using for the API has the correct permissions on the flow object itself.