Skip to main content
Level 1
January 22, 2026
Question

Hmm, looks like we hit a slight snag in this section

  • January 22, 2026
  • 1 reply
  • 33 views

I know I'm not the first to post about this error, but so far I haven't found any advice that helps.

 

I've entered all of my information and am ready to file, but I keep getting an error that says, "Hmm, looks like we hit a slight snag in this section." I tried waiting, tried switching from Firefox to Chrome, and then tried an incognito window. I've cleared my cache and cookies (which shouldn't be an issue, as I haven't used TurboTax before), but that also hasn't helped.

 

I'm using the free version, so it's not like it's getting hung up on my card info or because my antivirus is blocking anything in the billing. I'm also not on mobile but using my laptop.

1 reply

CatinaT1
Level 15
January 27, 2026

Sounds like something got stuck. You can try these things:

 

  • Log Out Completely: Before doing anything else, click Sign Out in the TurboTax menu.
  • Clear Cache and Cookies: This removes old, "corrupted" data that might be confusing the website.
  • Use an Incognito (Private) Window: This is the most effective "quick fix" because it launches the browser without any saved history or extensions (like AdBlockers) that often interfere with tax forms.
  • Check Pop-up Blockers: TurboTax often opens forms (like the 1099 PDF) or payment windows in a separate pop-up. Look at the right side of your address bar for a small icon with a "red X"—click it and select "Always allow pop-ups from Intuit."
  • Restart the Browser: Close all open windows of your browser entirely and then reopen it.

 

Most TurboTax errors happen because the browser is trying to use an old "session" from a previous visit. By clearing the cache or using Incognito mode, you force the browser to establish a brand-new, secure connection with the Intuit servers.

**Say "Thanks" by clicking the thumb icon in a post. **Mark the post that answers your question by clicking on "Mark as Best Answer"
Level 2
February 12, 2026

Clearing Cache worked for me.