Share via

Failed To Copy error when trying to copy Loop components or entire page

Anonymous
2023-04-21T00:11:15+00:00

Loop worked as expected for the first few days in our organization, but now whenever our pilot/test group attempts to copy a Loop component or use the "Copy as Loop Component" at the top of each page, we receive an error:

Failed to copy

Sorry, we are unable to reach the server right now. Please try again later.

All users in our test group are having the same experience. Not being able to copy components to other applications defeats much of the usefulness of Loop. Is there anything we can check in any logs to see if something's blocking traffic? We aren't having any other issues with M365 components, including Loop components in other apps (such as Teams). Just when working on items in loop.microsoft.com.

Session id: 0f450758-7893-407b-afe5-5e214b42edd1

App version: 20230328009.014

Microsoft 365 Insider | Loop | Windows
Microsoft 365 Insider | Loop | Windows
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.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-06-06T15:10:21+00:00

    I suggest starting by verifying the service health status of Microsoft Loop and related services in the Microsoft 365 admin center. Any reported issues or ongoing maintenance could potentially explain the "Failed to copy" error your pilot/test group is experiencing when attempting to copy Loop components or pages.

    Next, review your organization's network connectivity, proxy, and firewall settings to ensure they are not blocking or interfering with the communication required for Loop to function properly. Additionally, have all affected users clear their browser cache and cookies, and ensure they are using a supported and up-to-date browser version for Loop.

    Review the Loop service logs for any relevant error messages or clues that could help identify the root cause. Provide the session ID (0f450758-7893-407b-afe5-5e214b42edd1) and app version (20230328009.014) you mentioned to Microsoft Support, along with any error messages or logs.

    Should the issue persist after these troubleshooting steps, don't hesitate to contact Microsoft Support. Their team can provide further guidance or escalate the matter if it is a wider service-related problem. Resolving the inability to copy Loop components or pages is crucial for ensuring productivity within your organization.

    0 comments