Forum Discussion

mpros's avatar
mpros
Icon for Helper I rankHelper I
1 year ago

Warehouse forced migration concern - October Deadline

Dears,
as we approach the deadline on October of Datamarts (that are still working very well), I tried creating Warehouse + Gen2Flow with simple logic & queries, resulting in the folllowing error:

'Something went wrong, please try again later. If the error persists, please contact support.'. Codice di errore: UnknowErrorCode. (ID richiesta: ab444592-4458-4d10-9370-b53d86adc13b).

I'm concerned as I expect a block in data consumption.

Regards,
M

Need Help

11 Replies

  • rohit1991's avatar
    rohit1991
    Icon for Super User rankSuper User
    1 year ago

    Hi mpros 

    I’ve seen this error come up during the Datamart >> Warehouse migration. The message with UnknownErrorCode is pretty generic, but usually means the service can’t run the query against a Datamart anymore.

    A couple of things to try:

    • Make sure your workspace has Fabric enabled and that you are pointing the Flow to a Warehouse (not the old Datamart).
    • Re-create the Gen2Flow after provisioning the Warehouse  in many cases that clears the error.
    • If it still fails, raise a support ticket and include the error ID you shared.

    Since Datamarts are being retired in October, I’d recommend starting the migration to Warehouse now so you don’t hit a sudden stop in data consumption.

    • mpros's avatar
      mpros
      Icon for Helper I rankHelper I
      1 year ago

      Dear,
      as mentioned I'm facing the pre-mentioned issue while creating "Destination to Warehouse" Gen2Flow.
      I guess also it's fabric enabled, cause I have N datamarts deployed and working.
      Regards

      • rohit1991's avatar
        rohit1991
        Icon for Super User rankSuper User
        1 year ago

        Hi mpros 

        Thanks for clarifying. Since Fabric is enabled and your Datamarts are working fine, the issue is likely with how the Gen2 Dataflow is connecting to the Warehouse. A few quick checks:

        • Make sure the Warehouse is in the same workspace as your Dataflow.
        • In Dataflow settings, confirm that the destination is set to Warehouse (sometimes it defaults to Lakehouse).
        • Check that your workspace role is Contributor or higher, otherwise it won’t let you write.
        • Try a very simple test table to see if the issue happens with all loads or just your current one.

        If it still fails, it may be a current limitation with Warehouse + Gen2 Dataflows, so raising a support ticket would be the safest option.