Anyone else seeing/hearing of issues with sharing links lately?

%3CLINGO-SUB%20id%3D%22lingo-sub-2387377%22%20slang%3D%22en-US%22%3EAnyone%20else%20seeing%2Fhearing%20of%20issues%20with%20sharing%20links%20lately%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2387377%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20the%20past%20two%20weeks%2C%20we've%20had%204%20different%20people%20across%20our%20university%20report%20that%20%22some%20users%22%20have%20been%20unable%20to%20open%20sharing%20links%20to%20files%20or%20folders.%20In%20most%20cases%2C%20the%20share%20is%20created%20for%20%22people%20in%20your%20organization%20with%20the%20link%22%20and%20then%20sent%20to%20people%20who%20are%20definitely%20in-org.%20The%20people%20reporting%20the%20issue%20say%20that%20it's%20happened%20with%20multiple%20files%2Ffolders%20and%20is%20intermittent%2Finconsistent.%20For%20example%2C%20%22File%201%22%20is%20shared%20to%20people%20in%20the%20org%2C%20then%20the%20link%20is%20sent%20to%20some%20org%20users.%20Person%20A%20is%20unable%20to%20open%20it%2C%20but%20Person%20B%20can%20(again%2C%20both%20are%20org%2Ftenant%20users).%20%22File%202%22%20is%20shared%20the%20same%20way%2C%20and%20Person%20A%20can%20open%20it%2C%20but%20Person%20B%20can't.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOf%20course%2C%20we%20have%20been%20completely%20unable%20to%20accurately%20replicate%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2387377%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDocument%20Library%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPermissions%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Esecurity%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2388033%22%20slang%3D%22en-US%22%3ERe%3A%20Anyone%20else%20seeing%2Fhearing%20of%20issues%20with%20sharing%20links%20lately%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2388033%22%20slang%3D%22en-US%22%3EOne%20thing%20I%20noticed%20(which%20may%20or%20may%20not%20have%20any%20bearing)%20is%20that%20when%20you%20first%20generate%20a%20sharing%20link%20(either%20through%20the%20share%20icon%20or%20the%20copy%20link%20button)%2C%20the%20URL%20includes%20a%20query%20string%20at%20the%20end%3A%20%3Fe%3D%26lt%3B6%20random%20characters%26gt%3B%20(e.g.%3A%20%3Fe%3DYaMuAg).%20When%20you%20look%20at%20the%20link%20later%20(via%20%22Manage%20access%22%20panel)%2C%20that%20query%20string%20is%20not%20there.%20In%20one%20instance%2C%20a%20user%20who%20had%20trouble%20opening%20the%20file%20using%20the%20full%2C%20original%20URL%20(with%20that%20query%20string)%20was%20able%20to%20open%20it%20just%20fine%20by%20removing%20it.%20I%20don't%20know%20what%20the%20purpose%20of%20the%20query%20string%20is%2C%20but%20assume%20it's%20some%20sort%20of%20tracking%2Ftelemetry%20thing%20(e.g.%3A%20reporting%20back%20when%20the%20link%20is%20used).%3C%2FLINGO-BODY%3E
Regular Contributor

In the past two weeks, we've had 4 different people across our university report that "some users" have been unable to open sharing links to files or folders. In most cases, the share is created for "people in your organization with the link" and then sent to people who are definitely in-org. The people reporting the issue say that it's happened with multiple files/folders and is intermittent/inconsistent. For example, "File 1" is shared to people in the org, then the link is sent to some org users. Person A is unable to open it, but Person B can (again, both are org/tenant users). "File 2" is shared the same way, and Person A can open it, but Person B can't. 

 

Of course, we have been completely unable to accurately replicate the issue.

1 Reply
One thing I noticed (which may or may not have any bearing) is that when you first generate a sharing link (either through the share icon or the copy link button), the URL includes a query string at the end: ?e=<6 random characters> (e.g.: ?e=YaMuAg). When you look at the link later (via "Manage access" panel), that query string is not there. In one instance, a user who had trouble opening the file using the full, original URL (with that query string) was able to open it just fine by removing it. I don't know what the purpose of the query string is, but assume it's some sort of tracking/telemetry thing (e.g.: reporting back when the link is used).