March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
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
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
Solved! Go to Solution.
It appears this issue has now been fixed by Microsoft, so I am marking it as resolved
One of our semantic model data refreshes has suddenly started failing too (in the UK) with a circular dependency error. I don't think we're using any of the CALENDAR functions, though we do have some date manipulation so I may have missed one.
As with the others, refresh via desktop PBI works fine.
Same here. Reports using CALENDARAUTO() have stopped refreshing due to "Circular dependency"
We have this problem on all reports with aggregate tables. Not just data tables. We use aggegated tables on few other variables.
I have the same issue. I use Calenderauto in 100+ reports. Applying the workaround would be a lot of work and bad design. I hope this get solved asap.
I have same issue in UK across mulitpe reports. It started this weekend. PBIX refresh is ok and online not.
Hi All,
Regarding the semantic model refresh issue in the Power BI service, we have received reports of this issue and the team is actively working on it.
Current mitigation:
The issue can be mitigated by replacing the CalendarAuto function with the Calendar function.
If you are experiencing a similar issue, we recommend trying the above mitigations while we continue to update on the progress of the fix.
Thank you for your patience and support!
Any update for us?
Thank you for the update. Since the mitigation is not applicable in my situation (we didn't use CalendarAuto function but Calendar function), could you please provide an ETA for the fix?
Microsoft have acknowledged the issue and are currently working on a solution. Sadly they've not advised of a timeframe for resolution, though I will post here if I am advised of one
Do you know where they acknowledged this? A link would be good to drive additional comments from the community. Thanks for sharing!
Same issue is happening in AU too. It was working fine last firday but failed this morning. Tried a few workarounds mentioned in this post but none of them worked. I'm only using CALENDAR() for the calculated tables. Hope Microsft can fix this ASAP
The issue still persists in the UK. The solutions from the replies didn't help. We don't use CALENDARAUTO(), and changing the lookback to three years didn't make any difference. I wish Microsoft could look into it ASAP and revert the changes that followed the release of version 2.136.1478.0 on 08/10/2024.
I've changed mine from CALENDARAUTO( ) to CALENDAR( ) and all seems to be working now
I've had this in the UK too since yesterday for two of our reports, both use CALENDARAUTO to generate a date table and the circular reference is in the date table:
Desktop refresh works fine so I'm just manually refreshing and pushing up but hopefully it's a temporary glitch and will be resolved soon.
Yep, all of mine use calculated date tables and Calendar Auto function... I tested replacing the calendarauto with calendar function and it seems to refresh ok. However I'd rather not have to replace across all reports
Power BI support have suggested some code I can run for the workspace in SSMS which I will be testing in due course.
Thanks! If it doesn't resolve itself I'll make the change tomorrow
Managed to find a work around.
I also have a date table but date column is referenced from another table. Only thing I did was to remove duplicate and added some more date-related columns. I did not use calendarauto() or any other calendar functions. Therefore, I really don't know how to fix it even with your post. (T_T)
Funny thing is, I have other reports and dataset doing the same way but refresh is totally fine. All these datasets are in the same premium workspace, some datasets are fine, some aren't.
Hopefully Microsoft will come and fix this.
Hi @Bmann ,
In our test environment, the schedule refresh can be used normally, Microsoft Power BI Service status is also kept running, I do not know whether the past almost a day your problem has been resolved, I will keep following up on this issue, look forward to your reply!
Can we get any help with this? I can't open microsoft support ticket without fabric subscription
Good morning, sadly there is no change to the issue this morning - the Datasets continue to encounter the error when trying to refresh
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
37 | |
22 | |
20 | |
10 | |
9 |
User | Count |
---|---|
59 | |
56 | |
22 | |
14 | |
12 |