OneLake shortcut to Lakehouse SQL endpoint fails to create table
We have an Eventhouse database with a single table synced to OneLake. We've then created a table shortcut from the Eventhouse to a lakehouse - and everything works as expected: The table is visible in the lakehouse explorer, and can be queried using the SQL endpoint of the lakehouse. All good. A week later we then try to create another table shortcut from the eventhouse (same table) to a new lakehouse (in a different workspace). Now, the table is visible in the lakehouse explorer, but it fails to load the table to the SQL endpoint, giving the error in the image attached. The original (and completely similar) shortcut still works, and can be seen/queried in the SQL endpoint with data up to date. How can a shortcut work, and continue to work, when established at one point in time, but not a week later - when the source and destinations are structurally identical? All workspaces are hosted in the same region (West Europe).
