Circular dependency preventing scheduled refresh of data in Power BI service

[Bmann]

Hi, 

Never posted before but have a problem I can't get my head around... This morning I suddenly received failed to refresh notifications for many of our Power BI reports. The reports have been refreshing 3 times per day for several months without any issue until now.  

I have tried re-publishing the reports, sadly this did not help with the issue. The pbix files in the Power BI desktop refresh without any issues. 

The warning given states, "Something went wrong", "A circular dependency was detected..." 

The below post seems similar but does not have a clear solution, it appeared to resolve itself but I can't wait to see if that happens. 

Solved: Circular dependency in Service but not in Power BI... - Microsoft Fabric Community

UPDATE: Issue appears to be related to having a calculated table that uses the CALENDARAUTO DAX function

***UPDATE 18th OCTOBER***

The issue is now on the Microsoft Fabric support page and they're stating that it should be fixed by 20th October... No sign of it on the "known issues" section, but at least it looks like a resolution is due shortly.

link: Microsoft Fabric Support and Status | Microsoft Fabric

[dsj8wksnnckk]

Still encountering this bug-error in Serbia

[aartijethwani]

Still encountering the same issue here in Asia. 

[MRD87]

I fixed it by changing the relationships of the autocalendertable. The error occurs when the table has a one to one relationship. Fixed it by changing it to one to many.

[ChaosDivergence]

Thank you so much, this fixed it for me! Annoyingly it only started happening last week.

UK here.

[PatSz]

I tried same thing, but it does not allow me to change. It throws the Circular dependency error in relationships view as well...

[ChaosDivergence]

Try, instead of one to many, try many to one. That did it for me. The one side should be the calendar, the many side should be the other table.

[aartijethwani]

Getting the same issue since 14th Oct and theres no CALENDARAUTO reference being used. Any update on a possible workaround?

[Bmann]

***UPDATE***

The issue is now on the Microsoft Fabric support page and they're stating that it should be fixed by 20th October... No sign of it on the "known issues" section, but at least it looks like a resolution is due shortly.

link: Microsoft Fabric Support and Status | Microsoft Fabric

[primolee]

10/21 now and it still does not work...  I have not used calendarauto() and do not have one to one relationship.  Most of my BI are done with the same architecture but some work and some do not...

MS please fix this as soon as possible...  This is really frustrating... (T_T)

[Bmann]

Morning, are you sure the issue is still the same? I left a couple of my reports unchanged in order to test them, and they appear to be refreshing successfully, indicating that Microsoft have fixed the issue. Where in the world are you? I wonder if they could have rolled out the fix in stages? 

[primolee]

This morning I tried refreshed manually, and just now I tried again, unfortunately both failed.  I am in Taiwan (GMT+8), part of north Asia.  This is just sad... (T_T)

[xz2mo5]

i'm having this same issue still in the UK. none of our reports have had any changes made and the error code is the same.

[primolee]

Well, although I am in Taiwan, our host might be in UK as well, as our headquarter is in UK and they are in control of all the MS environment settings.

[WhyPBI]

I hope Microsoft addresses this soon. It's very frustrating for something like this to break without a quick fix.

[AlejandroVazque]

I have the same issue here in Luxembourg. I ahve several reports all having problems to refresh in PowerBI Service. The problem I cannot only use CALENDAR() function is because I'm using CALENDARAUTO(3) as my fiscal year is from April to March. Any help please or news form Microsoft how to solve this issue (relaibility is put into quesiton if reports work fine for years and suddenly stop refreshing because of a change like this CALENDARAUTO 

[onette40]

Has this already been resolved? I am still getting the error with my scheduled refresh.

[Bmann]

Sadly not - if your dataset contains a calculated date table using CALENDARAUTO, then you may be able to use a workaround by replacing this with the CALENDAR function and extending the date table to be for more dates than you'd need. Far from ideal, but it seems to allow for scheduled refreshes without error... 

[考林]

Same issues, have to manual refresh the reports in PBI desktop and publish it every day, hope Microsoft can reslove this issue ASAP.

[hsoto]

The same problem in Mexico, manually modifying each of the reports to replace calendarauto() is not an option. We need a response soon, please.

[hsoto]

This workaround worked for me, but it is really exhausting to do it in all the reports and then publish them...

DATE=CALENDAR(DATE(2000, 1, 1), DATE(2050, 12, 31))

[ChaosDivergence]

Thank you, that worked when changing the relationships didn't.