Resilience check failed: Mis tablas linked cross-capacity no se ven desde el SQL Endpoint

[Syndicate_Admin]

The error that appears is the following:

Resilience check failed: table change state is Unknown, indicating potential data inconsistency or storage communication issues

I've already tried:

Everything in this URL: https://community.fabric.microsoft.com/t5/SQL-database/Resilience-Check-Failed-Table-Change-State-Un...

Create the table, delete it, refresh it with %%SQL and with the Spark Engine.... Any ideas?

[v-dineshya · Accepted solution]

Hi @Syndicate_Admin ,

Thank you for reaching out to the Microsoft Community Forum.

1. Ensure the problem tables are Delta and don’t have problematic column names/blank line footers. Re‑write if necessary.

2. Check if the Lakehouse uses Schemas (Preview), If yes, test in a Lakehouse without schema preview and see if it appears in the SQL endpoint.

3. Verify permissions for shortcut source and destination, Grant Contributor on the source Lakehouse to the account that owns/uses the shortcut in the destination.

4. Programmatic refresh of the SQL endpoint, Call Refresh SQL Endpoint Metadata via REST, you can do it from a notebook or a pipeline Web activity. This is key when the UI refresh won’t clear the unknown state.

5. If still failing, Materialize into a new Delta table inside the Lakehouse (Copy/Dataflow Gen2) and refresh again. This removes reliance on external _delta_log lineage.

Please refer below links.

Solved: Re: Lakehouse Tables Not Appearing in SQL Endpoint... - Microsoft Fabric Community

Solved: Re: Lakehouse tables not showing up in SQL Endpoin... - Microsoft Fabric Community

I hope this information helps. Please do let us know if you have any further queries.

Regards,

Dinesh

[v-dineshya]

Hi @Syndicate_Admin ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

Regards,

Dinesh

[Syndicate_Admin]

Hello, option 5 that you have given me has been the one that has worked, unfortunately it happened with the more than 120 tables we had so there was a lot of rework to do ... But in case it happens to anyone else, option 5 was the one that worked for me!

Thank you very much @Syndicate_Admin for the help!

[v-dineshya]

Hi @Syndicate_Admin ,

Thanks for the update. We are happy to hear that your issue got resolved . please let us know if you still need any help, we are happy to assist you. Please continue to utilize Microsoft Fabric community.

Regards,

Dinesh