Can someone help with Dropbox error 8737.idj.029.22?

General
1

I’m having trouble with Dropbox error 8737.idj.029.22 and can’t access or sync some of my files. It started suddenly, and basic troubleshooting hasn’t fixed it. I need help figuring out what this error means and how to fix it so I can get back to my documents.

2

8737.idj.029.22 does not look like a standard public Dropbox error code. When Dropbox throws odd mixed codes like this, the cause is often one of 4 things. Corrupted local cache, a stuck sync database, a blocked file path, or security software blocking Dropbox.

Try this in order.

  1. Check Dropbox Status page.
    If sync services are down, wait. Rare, but it happens.

  2. Pause Dropbox, then quit it fully.
    On Windows, end Dropbox.exe in Task Manager.
    On Mac, quit from Activity Monitor if needed.
    Then reopen it.

  3. Look for bad file names.
    Dropbox often fails on:
    Files with trailing spaces.
    Names with reserved characters.
    Paths over about 260 chars on older Windows setups.
    Temp files from Office or Adobe.
    Try moving one affected file to a short path like C:\Test.

  4. Check disk space.
    Dropbox needs free local space for sync and indexing. If your drive is near full, sync errors show up fast.

  5. Clear the local Dropbox cache.
    Open your Dropbox folder.
    Find .dropbox.cache.
    Delete its contents, not your real files.
    This fixes a lot of weird sync bugs.

  6. Relink the app.
    Sign out of Dropbox in Preferences.
    Sign back in.
    If needed, unlink and relink the device from your account page.

  7. Disable antivirus or firewall for 5 minutes.
    A lot of third-party AV tools block Dropbox writes. Seen this with Bitdefender, Avast, and some corporate endpoint tools. Re-enable after testing.

  8. Check permissions.
    Make sure your user account owns the Dropbox folder and has read/write access. On Windows, right-click folder, Properties, Security. On Mac, Get Info, Sharing & Permissions.

  9. Use selective sync.
    If only some folders fail, unsync them, let Dropbox settle, then resync. Crude, but it works more often than it should.

  10. Reinstall Dropbox cleanly.
    Uninstall it.
    Delete leftover Dropbox app data.
    Reinstall the latest build.
    Do not delete your cloud files. The local index gets rebuilt, which fixes db corruption a lot of the time.

If none of this helps, post 3 details.
Your OS and version.
Whether web access to those files still works.
Whether the problem hits all files or only a few.
Also check the Dropbox logs folder. There’s usuallly a clue in there.

3

8737.idj.029.22 honestly looks less like a real Dropbox code and more like an internal app/log identifier that bubbled up to the UI. So I’d stop chasing the exact code and try to figure out where the failure is happening.

A couple things I’d check that @nachtschatten didn’t really get into:

  • Test Dropbox on the web with the same files. If they open fine there, your cloud copy is probably okay and the issue is local app/database/OS related.
  • Check if the affected files are online-only, locked by another app, or sitting in a folder that got moved by OneDrive/iCloud/Desktop/Documents backup stuff. That cross-sync conflict causes weird errors all the time.
  • If you’re on Windows, look in Event Viewer around the time the error started. On Mac, Console. You may see filesystem or permission errors Dropbox itself hides.
  • See whether the files are actually blocked by Windows. Right click file, Properties, and look for an “Unblock” checkbox.
  • Run a disk check. Not glamorous, but sudden sync weirdness can come from file system errors.
    • Windows: chkdsk /f
    • Mac: Disk Utility > First Aid

One place I kinda disagree with @nachtschatten: jumping to reinstall too early can waste time if the real problem is a bad drive, account restriction, or another sync service interfering.

Also worth checking:

  • Dropbox account storage full
  • File ownership changed after OS update
  • VPN/proxy/filtering DNS breaking API calls
  • Team/business admin restrictions if this is a work account

If you can, post:

  • Windows or macOS version
  • Dropbox app version
  • Whether web access still works
  • Exact behavior: “can’t open,” “won’t sync,” or “shows missing”
    That’ll narrow it down prety fast.
4

That code smells like a corrupted local Dropbox index more than a true “file is gone” problem. I slightly disagree with @nachtschatten on one point though: Event Viewer and disk checks are useful, but before digging into OS logs, I’d test whether Dropbox is failing only on one path type.

Try this:

  1. Create a brand new folder at the root of Dropbox.
  2. Put in one tiny test file like a .txt.
  3. Rename it with a very short name.
  4. See if that syncs.

Why this matters:

  • If new files sync, but old ones do not, the issue is often path length, invalid characters, or a stuck namespace.
  • If nothing syncs, it is more likely the local Dropbox client state is broken.

Things not mentioned yet that are worth checking:

  • File path too long on Windows
  • Reserved characters in filenames: * ? < > : |
  • Case-only renames from Mac to Windows causing sync stalls
  • Selective Sync accidentally removing the folder locally
  • Extended attributes or package-style folders on macOS confusing Dropbox
  • Antivirus quarantining Dropbox temp files

A good next move is a Dropbox app reset, not a full reinstall. Reinstalling sometimes preserves the same bad cache. Resetting forces a cleaner rebuild of metadata.

Pros for ‘’:

  • Can improve readability if you are documenting the issue
  • May help organize troubleshooting notes

Cons for ‘’:

  • Not relevant unless you are tracking lots of test results
  • Won’t fix the sync bug itself

Also check the Dropbox sync icons carefully. “Syncing,” “offline,” and “available online” get mixed up a lot and point to very different causes. If you can say whether the files fail on rename, open, move, or upload, that will narrow it down fast.