Microsoft Loop stuck: how to get it moving again

If Microsoft Loop is stuck, the safest first fixes are to refresh the page, check Microsoft 365 status, and try the page in a private window or another browser before you touch site data or anything broader. In most cases, the freeze comes from the browser, a stale page state, a slow connection, or a Microsoft service issue rather than lost content. Start with the low-risk checks below, then confirm the page loads and syncs normally before you keep editing.

What 'stuck' in Microsoft Loop usually looks like

“Stuck” can mean a few different things in Loop. You might see an endless loading spinner, a page that opens but won’t respond to typing, a component that looks frozen after you paste content, or changes that seem to save on your screen but never show up for teammates.

It can also show up as lag instead of a hard freeze. For example, you type a few words and they appear several seconds later, or the page scrolls but clicks don’t register. Sometimes the page looks normal, but another person’s edits never arrive, which makes it feel like sync is broken.

If you’re working in a shared page, the problem may be limited to one page or one component rather than all of Loop. That matters, because a single bad page state is handled differently from a browser problem, a network issue, or a wider Microsoft service outage.

When this problem is just Loop, and when it’s something else

Before you change anything, work out where the failure is happening. The main possibilities are a Microsoft service issue, your browser, your network, or a bad page or component state inside Loop.

Use these quick checks:

• If Loop won’t load in any browser, on any device, and coworkers have the same issue, suspect Microsoft 365 or Loop service trouble.
• If the page works in another browser or an incognito/private window, the problem is usually browser cache, extensions, or stored session data.
• If other websites are slow too, the network is the likely cause.
• If only one page or one embedded component is frozen, the issue is often limited to that item.

Before you start: This applies to Microsoft Loop in Microsoft 365 on web and desktop browsers. You usually do not need administrator rights for the first checks. You do not need to restart your PC right away, and you should avoid clearing site data until you’ve confirmed the issue isn’t just a temporary load problem.

If you are editing content that matters, pause before doing anything that might discard a draft. Make sure the last visible changes are on screen, and if possible leave the tab open while you test another browser or device.

The safest fixes to try first

Start with the least risky options. These won’t normally overwrite content, and they’re reversible.

1. Save what you can see, then wait a moment.

If the page is half-loaded but editable, stop typing for a few seconds and give Loop time to sync. Sometimes the issue is just delayed rendering.

2. Refresh the page.

Use the browser refresh button, or re-open the tab if refresh doesn’t respond.

Browser toolbar > Reload

The page should reload and your content should appear again. If the same spinner or freeze returns, the page state is probably still stuck.

3. Try a private or incognito window.

Open the same Loop page there and sign in again if prompted.

Browser menu > New InPrivate window / New incognito window

If it opens cleanly there, the browser cache, cookies, or an extension is probably involved. If it fails there too, the problem is less likely to be local to that browser profile.

4. Switch browsers.

Open the page in another supported browser on the same device. This helps separate a Loop issue from a browser-specific issue.

If the page works in one browser but not another, keep using the working browser for now and treat the failing one as the problem.

5. Check Microsoft 365 status.

If you have access to the service health page for your tenant, or if your IT team has posted an outage notice, check that before you clear data or reinstall anything. A service incident can look exactly like a frozen page.

If the status page shows an issue, stop troubleshooting locally and wait for the service to recover unless IT asks you to keep testing.

6. Clear cached site data only if the page still hangs.

Do this from the browser settings for the Loop site, not by wiping everything if you can avoid it.

Browser settings > Privacy and security > Site data / Cookies and site data > Search for the Loop or Microsoft 365 site > Remove site data

If the page starts working after that, the issue was stale local data. If it still fails, the problem is probably outside your browser cache.

Do not uninstall the browser, sign out of all Microsoft accounts at random, or clear every site’s data first. Those steps are broader than you need and can create more work if you have other tabs or sessions open.

How to know Loop is working again

Don’t assume the fix worked just because the page opened once. Confirm that Loop is responding and syncing.

Check these three things:

• The page loads without a long spinner or blank area.
• You can type, delete, and move the cursor without delay.
• A small edit appears for other people, or you can refresh and still see your own change.

If the page is shared, make one harmless test change, such as adding a short word to a noncritical line, then refresh the page after a few moments. If the edit is still there after reload, that’s a good sign the page state is stable again.

The page opens normally, edits appear right away, and the same content is still there after a refresh.

If edits only seem to work until you refresh, the browser may still be holding a local view that isn’t syncing properly. If teammates still can’t see updates, the problem may be account-specific, permission-related, or tied to the service side rather than your device.

How to avoid getting stuck again

A few habits make Loop less likely to freeze on you during a busy day.

Keep one main browser session open for the work you’re actively editing. Jumping between many signed-in sessions can confuse page state and make sync look unreliable.

Avoid multiple people editing the exact same small section at the same time if you can help it. Loop is built for collaboration, but a crowded section can still be messy if several people are typing in the same spot.

If you move between devices, wait for your latest edits to appear before switching. A quick refresh before you close the first device helps confirm the work has synced.

If the same page keeps getting stuck, treat that page as the problem instead of your whole account. Copy the content to a new page only after you’re sure the old page has stopped updating, and let IT know which page, component, and browser were involved.

If the same issue keeps coming back on the same page, stop using that page for live edits until someone can check it.

Conclusion

If Loop is still stuck after a refresh, a private window, and a browser switch, stop pushing on the same page and check Microsoft 365 status or contact your IT team. Keep the tab open if you can, because that makes it easier to compare what you see with what they see. Once the page loads, edits save, and refreshed content stays in place, you can go back to work.

Frequently Asked Questions

Why does Microsoft Loop keep loading forever?

That usually points to a browser session problem, cached site data, a slow or unstable connection, or a Microsoft service issue. If it happens only on one page, the page state itself may be stuck.

Will refreshing Loop lose my work?

Usually not, but don’t refresh while you have unsaved text still appearing on screen or before you’ve paused long enough for it to sync. If the page is actively frozen, try a quick wait first, then refresh.

What should I try first if a Loop component won’t update?

Refresh the page, then open it in a private window or another browser. If that works, clear only the site data for the Loop or Microsoft 365 site.

When should I contact IT?

Contact IT if the same issue affects multiple people, if Loop fails in more than one browser or device, or if Microsoft 365 status shows an incident. Also escalate if the page is shared and edits still do not sync after the basic checks.