Share via

Power Automate “When a task is assigned to me” trigger is delayed/inconsistent for Planner → To Do sync

Stewart, Chad 0 Reputation points
2026-05-19T20:54:08.19+00:00

I have a Power Automate flow configured to create a duplicate Microsoft To Do / Outlook task whenever a Planner task is assigned to me. The goal is to make Planner tasks visible in the Outlook To Do pane so I can drag them into my calendar for timeboxing.

The flow generally works, but the trigger behavior is inconsistent.

Issue:

  • The trigger is “When a task is assigned to me” (Planner)
  • The flow checks every 5 minutes
  • Sometimes when I assign myself to a Planner task, the flow does not execute immediately
  • In many cases, the task will not sync until 30–60+ minutes later
  • Occasionally it appears to miss tasks entirely

Current flow logic:

  • Trigger: When a task is assigned to me
  • Action: Create Outlook task / To Do task
  • Includes title, due date, and task details

Screenshots attached below:

Microsoft 365 and Office | To Do | For business
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ryan-N 13,335 Reputation points Microsoft External Staff Moderator
    2026-05-19T21:24:05.1033333+00:00

    Hi @Stewart, Chad,

    Welcome to the Microsoft Q&A forum.

    Thank you for contacting us.

    Since our current scope of support is primarily focused on Microsoft 365 products, while the issue you're experiencing is with Microsoft Power Apps, I want to make sure that you receive the most accurate and effective support. For this reason, I recommend that you post your question in the Microsoft Power Platform Community Forum:

    Microsoft Power Platform Community Forum Thread

    There, you will be able to receive answers from the appropriate specialized team, and other partners who regularly follow the forum will also be able to share their experience or benefit from your case.

    I apologize for directing you to another community, but since the scope of this category is primarily focused on Microsoft 365, my knowledge of Power Apps is limited. Guiding you to the most suitable resource will help you get faster and more accurate support.

    If you have any questions or need further assistance, please feel free to share them in the comments on this post so I can continue to support you.

    I look forward to continuing the conversation.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments

  2. AI answer

    2026-05-19T20:54:25.79+00:00

    The behavior comes from how Power Automate triggers work rather than from the To Do action.

    For this flow:

    • “When a task is assigned to me” is a polling trigger.
    • In Code view the trigger shows a recurrence block with frequency and interval.
    • Polling triggers only check for new events on that schedule and can also be affected by throttling and service communication issues.

    When the run history shows many runs with Status = Skipped, it means the trigger check ran but the trigger condition was not met at that time, so the flow did not start. The task then appears to “sync late” when a later poll finally sees it, or appears to be “missed” if the trigger never sees it within the polling window.

    To troubleshoot and mitigate:

    1. Confirm the trigger is polling and review its interval
      • In the trigger’s Code view, verify the recurrence section and its interval/frequency values. This defines how often the trigger checks for new Planner assignments.
      • A 5‑minute interval is the minimum supported here; it cannot fire in real time.
    2. Check for skipped trigger checks
      • In Power Automate, open the flow and go to 28‑day run history → All runs.
      • For times when a run was expected but did not occur, look for entries where the trigger check was Skipped. This indicates the trigger condition was not met at that time.
      • If the Planner assignment happened between polls or Planner was slow to surface the change, the trigger will not see it until a later run.
    3. Review trigger conditions and inputs
      • Open the trigger, go to Settings → Trigger conditions.
      • If any conditions are configured, verify they match the actual Planner data so that valid assignments are not filtered out unintentionally.
    4. Consider platform limits and throttling
      • If many flows or Planner operations are running, connector calls can be throttled, which delays trigger execution. Manually testing the flow (Run → Test) can help confirm whether throttling is involved: if a manual run fires immediately, throttling is less likely the cause.
      • Use Power Automate analytics and the guidance in “Understand platform limits and avoid throttling” to reduce actions or split flows if necessary.
    5. Check for service or connection issues
      • Delays can also be caused by temporary communication problems, outages, or expired authentication. Use Help + support in the Power Platform admin center to see if there are active outages, and refresh the Planner connection if needed.

    Because this trigger is inherently polling and subject to these limits, it cannot be made truly real‑time. The most that can be done is to ensure the recurrence is set as low as allowed, verify no trigger conditions are unintentionally skipping events, and monitor for throttling or service issues.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.