Microsoft planner

Question

When I or someone else tries to add a task to me in the Microsoft planner an error appears: You no longer have access to the object “here is task title”.Technical details

Correlation tag: d82fc118-4f0b-4848-824f-c8abde8be289

Time reference: 2024-11-28T07:59:19.233Z

I've checked all my plans and I have acces to them. I can see all the tasks but I cannot be added to them. I will be grateful for any help.

Answer 1

Dear Marta Kuklik,

Thank you for sharing the details of the issue you’re facing in Microsoft Planner. Based on the information provided, your account may have a permissions or synchronization issue. Here are some steps to resolve this:

1. Check Group Membership

• Verify that you are still a member of the Microsoft 365 Group associated with the Planner. If your membership was removed or altered, it could affect your ability to be assigned tasks.

2. Verify Assigned Role

• Confirm that you have the appropriate role (e.g., member or owner) in the group. Insufficient permissions might prevent others from assigning tasks to you.

3. Clear Browser Cache

• If you are using Planner via a browser, clear the browser’s cache and cookies, then log in again to ensure no local data issues.

4. Test in a Different Environment

• Try accessing Planner on another browser or the Microsoft Teams app to rule out device-specific issues.

5. Check Planner Limits

• Ensure the task or plan is not exceeding the Planner’s limits (e.g., a maximum of 2,000 tasks per plan). If the plan is at its limit, adding or assigning tasks might fail.

6. Reconnect Planner

• If you use Planner within Microsoft Teams, remove and re-add the Planner tab to refresh the integration.

7. Contact the IT Administrator

• If the issue persists, your organization’s IT administrator can check the Microsoft Admin Center for any configuration or permission issues specific to your account.

8. Provide the Correlation Tag and Timestamp

• When contacting Microsoft Support, include the correlation tag (d82fc118-4f0b-4848-824f-c8abde8be289) and timestamp (2024-11-28T07:59:19.233Z). This helps Microsoft pinpoint the error in their logs.

I hope this helps resolve the issue quickly. Please let me know if you need any more clarification.

Kind regards,

Yuki