Forum Discussion
OData 503 Error in Power BI When Using Custom Parameter from Azure DevOps
Hi GuilhermeMorett ,
Thank you Naila-Rais and anilelmastasi for the insightful responses!- When using $expand, ensure you're selecting only the necessary fields to reduce the complexity of the query. This can help mitigate performance issues and potential 503 errors.
- Instead of expanding the parent work item within your main query, consider executing a separate query to fetch the parent work item's custom date field. You can then merge this data with your child work items in Power BI.
- Be aware of Azure DevOps service might limits and throttling policies. Exceeding these limits might result in 503 errors. It's advisable to pause operations and retry after some time.
Hope this resolve your query.If so,give us kudos and consider accepting it as solution.
Regards,
Pallavi G.
Hello GuilhermeMorett ,
Thank you for detailed description of your issue. Custom fields on Azure DevOps OData are often slower or less stable because they are pulled from an extended schema. Not all custom fields are fully exposed or optimized in the OData layer. OData feed performance degrades with wide and complex queries, especially when many fields are included, and especially across large datasets. 503 error usually means the backend service is overwhelmed or unable to process your request. When you include the custom parameter (especially if it’s a custom Date field), the OData query becomes more complex, and the API may hit resource limits, take too long to respond (timeout) or hit throttling thresholds.
To fix this you may reduce the scope of the query
Try pulling only the ID and the custom field (Custom Date) — no other columns — and test if that works.
This helps isolate if the problem is the field itself or the combination of fields.
If this solved your issue, please mark it as the accepted solution. ✅
Hi anilelmastasi !
The suggestion given helped solve the problem.
I added WorkItemType and Status in my case to reduce the amount of returns and jobs.
I was using one query with all the parameters I needed (including the custom parameter), but now I split one query for the custom parameter and another query for the other parameters.Fun fact:
I had been using the full query for a few months without any problems, but overnight this error appeared.
