"Number of queries exceeded. Delete few queries before creating new queries" When accessing microsoft partner API

Anonymous
2023-03-03T09:05:58.1666667+00:00

Hey, I keep getting this Error when connecting to the Microsoft Partnercenter API.

The Pipeline worked before...this problem occured just recently. When I try deleting the Scheduledqueries I also get an Error.... Has anybody got an Idea how I can fix this.

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
9,514 questions
Microsoft Partner Center API
Microsoft Partner Center API
Microsoft Partner Center: A Microsoft website for partners that provides access to product support, a partner community, and other partner services.API: A software intermediary that allows two applications to interact with each other.
312 questions
{count} votes

1 answer

Sort by: Most helpful
  1. MartinJaffer-MSFT 26,021 Reputation points
    2023-03-08T23:46:16.5966667+00:00

    @Anonymous Hello and welcome to Microsoft Q&A.

    As I understand you are using Data Factory pipelines to make calls to "Microsoft Partner" api.

    From what I can see, the "number of queries exceeded" error is coming from the Microsoft Partner api, not an error of Data Factory.

    I have never looked at Microsoft Partner Center before. From what I gather from documentation, and your error, here is what I suspect is happening.

    From the pipeline, you are calling the "create report query" which creates a template. Then you are calling the "create report" which schedules the query to run. After this pipeline running enough times, you hit some limit (I haven't found document on that). After hitting this limit, you get the reported error.

    When you tried to delete the "scheduledqueries", you tried to delete the template underlying a scheduled report. A report needs a query in order to run.

    You need to delete the report first, then you can delete the query. Then you will have a free slot for new queries.

    This is my best guess at what is happening.

    0 comments No comments