Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Solved
Persisting "We've interrupted your sharing activity" error.
Hello,
When I try to share any file I get an error "We've interrupted your sharing activity. For details or to contact support read our help center article".
I read the article and I can't find a...
Hannah
Dropbox Community Moderator
Dropbox Community ModeratorThanks for letting us know, ericbonsaify1.
Have you also received some kind of email notification about your sharing activity or is it just the desktop notifications?
Just desktop. Although I had wondered if it had to do with storage space, but I have 200GB free so seems unlikely. If you can assist in fixing it that would be great.
- Nancy
Hey ericbonsaify1! Can you please check the email address that’s linked to your Dropbox desktop app and make sure it’s the exact same as the one you see here?
If your sharing activity has been paused for the time being, you should be seeing the same error across all Dropbox platforms.
Let me know what you find.
The email does match exactly (although I did change the account email I believe a couple years ago). As for sharing being paused - the link you included does not mention 'Pause' on the page and I'm not seeing any of those errors. I do have active shared folders.
- Nancy
Thanks for double checking your email address, ericbonsaify1. The Help Center article I linked above includes all the possible reasons why the sharing activity of your Dropbox account could’ve been interrupted (which is also the error you keep receiving). However, since you’re only encountering this error on the desktop app, we’ll investigate this further.
To clarify one more thing; you mentioned above that this is happening when saving screenshots to your Dropbox account, correct? Does this occur when saving any other type of file to your Dropbox account?
If not, I’d like you to disable the “Save screenshots to your Dropbox” setting on your computer, restart your device and then, enable it again. Do you keep getting the same error message after that?
