A collaborative workspace app in Microsoft 365 designed to help teams co-create, stay organized, and work together in real time across apps and devices.
Hi,
Loop task lists and action items created from meeting notes sync with Microsoft Planner. As a result, the reminder emails are handled by Planner notifications rather than by a separate Loop-specific reminder system.
Reminder emails may not be delivered at the exact same time or frequency for every user because notification behavior can depend on each individual user’s Planner notification settings, Teams notification settings, and the task details themselves. For example, the task must be assigned to the correct user, have a due date, and remain incomplete for due-date reminders to apply.
To help ensure a more consistent experience, I recommend that each assignee checks the following:
- Open Microsoft Planner.
- Go to Settings > Notifications.
- Confirm that notifications are enabled for:
- Tasks assigned to them
- Tasks that are due soon, due today, or overdue
- Confirm that the task in Loop/Planner is assigned to the correct user account.
- Confirm that the task has a valid due date and is not already marked complete.
- Check Teams Activity Feed settings as well, since Teams notifications are managed separately from Planner email notifications.
At this time, there is no Loop-level admin setting that enforces a single reminder cadence for all users. If your team requires a fixed reminder schedule, such as a daily reminder at a specific time, I recommend using Power Automate to create a custom reminder flow based on the synced Planner tasks.
For more information, please refer to the following link:
- Manage your tasks from Loop Task lists and Collaborative notes in Planner
- Stay updated with notifications in Planner
Given that your question involves a combination of Microsoft Loop and Power Automate workflow design, the most suitable place to receive specialized guidance would be the Microsoft Power Platform forum. Experts in that community can help explore alternative governance strategies, provide insights into unsupported API behavior, and monitor whether channel‑level archiving becomes supported in future Graph API updates.
I hope this explanation helps clarify why the archiving operation is not working and assists you in determining the next steps for your process. If you find this response helpful, please consider marking this answer as "Yes", so others in the community with the same question can benefit.
Thank you again for participating in the forum, and please feel free to reach out anytime if you need further assistance.
Note: Please follow the steps in forum documentation to enable e-mail notifications if you want to receive the related email notification for this thread.