When building out our dataflows, we are repetetively receiving the error when reading data from the Azure Databricks connector
- "The import Databricks.Catalogs matches no exports. Did you miss a module reference?"
This doesn't happen all the time, but periodically, sometimes fixing itself the next day. The strange thing though is that we can have the following situation
- one dataflow can exhibit this behaviour
- we then can create another dataflow that will then work fine sourcing from the same table
- we can copy the m code from the working connector to the original that is not working and it does not fix the issue
This is affecting our production loads, and we would like to find a resolution asap
