Due to the 50times/1min/user limit in the Pubric API, HTTP status code 429 (Too many requests) occurs when triggering BLOB events or executing the REST API.
Using API :
https://learn.microsoft.com/en-us/rest/api/fabric/core/job-scheduler/get-item-job-instance?tabs=HTTP
https://learn.microsoft.com/en-us/fabric/data-factory/pipeline-rest-api#get-item-job-instance
The Cx business scenario should guarantee at least 300times/1min/user execution, but the current API integration situation does not seem to support this.
To address this issue, we propose the development of an API that can handle a higher volume of requests and provide comprehensive details without the current restrictions.
This enhancement would greatly benefit users by improving efficiency and enabling more robust data management capabilities
NaamaTsafrir
on:
Detect and control unused Fabric/Power items in th...
on:
Auto-Spacing Option Between Visuals When Aligning ...
on:
In "Manage relationships" view I need to filter by...
ToddChitt
on:
The list of available connections via a pipeline C...