Issue Summary

The root cause of HOT-117114 is that a query which passes the draft share id to the backend was created which simultaneously ran with another query with the draft share id. Both queries required permissions to be added, but the second one to complete threw an exception due to the permissions already being in the database. The exception caused the "Stumbled Upon Restricted Content" screen to be displayed on first draft share, even when it was not restricted content.

We don't have automated monitoring or testing of any kind that tells us when the draft share page stops working in production. During the HOT, all first draft shares threw the Stumbled Upon Restricted Content screen. Please add testing or a pollinator to automatically alert when this flow fails.

Steps to Reproduce

During the HOT any first share of a draft threw up the Stumbled Upon Restricted Content screen the first time any individual user tried to access the URL with the shared draft id in it.

Expected Results

There should be no Stumbled Upon Restricted Content — there isn't anymore due to a mitigation given during the HOT; but we want to find out if there was a specific change which caused the problematic behavior.

Actual Results

The Stumebled Upon Restricted Content screen was shown during the first load during the HOT.

Workaround

We made a patch to the backend that circumvents this, though not super cleanly. Also, reloading the page causes the Stumbled Upon Restricted Content screen to go away.