PowerBI connection broken? Bad gateway error 502

Hello. Today I tried to refresh my PowerBI report which I have connected to Orkestra utilization data via the “Copy Power BI URL” option. When trying to refresh the queries I get an error on the Orkestra data source:

I checked with a colleague if he would get the same error as well and he is also getting it on his side at a different PowerBI report.

Is this a problem from our side or maybe Orkestra side? Thanks.

Hey there @FilipeFinco
Let us take a look and report back

@FilipeFinco this should now be resolved.

please let us know when you get to try it out !

I am still getting the same error.

this appears to be more of a timeout due to the amount of data. we’re going to run more tests and report back.

Indeed there’s a limit hit because of the amount of data.

Please try adding a startDate parameter in the Api query.

It works like this for data from beginning of the year :

https://api.orkestra.online/prod/Analytics/OrkstraUsageAnalytics?userId={your guid}&startDate=2026-01-01

I added the start date to match the first entry on my utilization logs, but now I get a different error: (500): Internal Server Error

1 Like

The date given here is a very long time ago and is equivelent to no date at all (retrieves all the data). That’s why it still times out with it. Can you try 2026-01-01 (for data from the start of this year) ?

You may need to implement per-year queries in powerbi , it’s pretty straignforward to setup!

I changed the start date to 2026-01-01 but all logs are coming in with null values now:

Looks like the log column names changed?

can you try and type the url in a browser and see what it looks like? It should normally look correct.

Your screenshot looks like there might be something wrong in the powerbi side of things where it has lost its json to table data conversion logic :thinking:

Looks like this in the browser:

yes looks correct.

And also yes just saw your other screenshots in your previous post, there’s a camelcase naming issue let us resolve this very quick .

1 Like

oaky how about now? :slight_smile:

1 Like

Yes, now I got the logs to show up again with start Date 2026. Now I need to figure out how to implement the per year queries, but I would like to be able to make it in a way that all years can get combined into a single list, just to keep the logic of my current report and visuals.

you can add queries to your power bi project.

You can have

2024 data : https://api.orkestra.online/prod/Analytics/OrkstraUsageAnalytics?userId=&startDate=2024-01-01&endDate=2024-12-31

2025 data : https://api.orkestra.online/prod/Analytics/OrkstraUsageAnalytics?userId=&startDate=2025-01-01&endDate=2025-12-31

etc. in the same project .

then go to Transform Data

then append queries

You’ll be able to have many querries in the same Data Table.

1 Like

Thanks @m.elayoubi for the help and quick response! I managed to split the queries by year and append them back into one table. There were some tweaks I had to do in the data types for everything to work again but in the end we managed!

So I guess we know the limit - 106.000 entries in 5 years :stuck_out_tongue:

I wonder if that is a lot or not. We expect utilization to grow in the next year as more people in the organization will be granted access to the automations. Hopefully the per year queries continue to hold!

1 Like

That is a pretty cool number haha :smiley: above average that’s for sure, especially in recent years! That’s proof that you’re doing it right !! awesome work!!

1 Like