'Couldn't copy, but it might be a fluke. Try reloading the page or ask us for help' error

[CJZ]

Hi guys,

Our company account has been suffering from a "Copy Link" failure issue for months.

The symptom is we can't use the "Copy Link" function.

Every time the user inside the enterprise plan tries to use the "Copy Link" function, then the system will say: "Couldn't copy, but it might be a fluke. Try reloading the page or ask us for help".

The service team said they were investigating the issue.

But still no solutions.

Does anyone have any idea about this?

[Hannah]

Thanks for bringing this to our attention, @CJZ.

Can you please give us the ticket number of the communication you had with our support team, so we can investigate further?

Thanks in advance!

[CJZ]

Hi Hannah,

Thank you for your reply.

ticket number of the communication：

Ticket #22433632: Dropbox Support Chat

Ticket #22417501: Dropbox Support Chat

CJ

[Hannah]

Thanks for the ticket numbers, CJ.

From what I can see, your second ticket closed, as you didn't reply back to the agent with the info they requested.

Even though the ticket is closed, can you try replying back to that email, to open a new follow-up ticket?

That way our support team will be able to assist you directly.

[AIRRTeam]

Within the last 24hours, I've been getting this error message when trying to create a new share link or copy share a link which has already been generated?

"Couldn't copy, but it might be a fluke. Try reloading the page or ask us for help." - this is the exact error message. Refreshing does nothing and there's just no answers that directly link to this currently. Have not a received an email detailing if it was a ban or anything else. 

Any ideas or solutions?

[Hannah]

Thanks for letting us know, @AIRRTeam.

Have you tried using a different browser or a private browsing window, to see if that helps?

Keep me posted.

[AIRRTeam]

Yes, have tried chrome, incognito mode on chrome, firefox and edge. 
Dropbox app on Mac also produces the same error. No amount of refreshes has solved the issue.

[Megan]

Hi @Elaine C.4, interesting. 

Can I send you an email, in order for us to have a closer look into this? 

[AIRRTeam]

Hi Megan,

Sure thing. You can email me. 

Just wanting to give you an update, this issue has mysteriously resolved itself yesterday. 

However, the down time of more than 24 hours, was very concerning as it impeded our team from sharing any files during that time with no way of resolving the issue. 

[Megan]

I just sent you an email @Elaine C.4, see you there!