Forum Discussion
https://api.fabric.microsoft.com/v1/admin/items REST API does not work
Previously Rest API used to work and now it returns Response Code: 400
Could you please provide an information if there are any features related to move it from Preview to Prod
Hi everyone,
I wanted to share an update on my investigation.
I identified that the error is occurring when the API tries to retrieve an item that has already been deleted. During the pagination process in the Copy Data activity, the pipeline attempts to access a resource that no longer exists, which results in a 404 NotFound (EntityNotFound) error.
Here is an anonymized version of the error message for reference:
"errors": [
{
"Code": 23353,
"Message": "Failure happened on 'Source' side. ErrorCode=RestCallFailedWithClientError, Type=HybridDeliveryException, Message=Rest call failed with client error, status code 404 NotFound.\nRequest URL: https://api.fabric.microsoft.com/v1/admin/items? <suppressed parameters>.\nResponse: {\"requestId\":\"<ID_anonymized>\",\"errorCode\":\"EntityNotFound\",\"message\":\"The requested resource could not be found\",\"relatedResource\":{\"resourceId\":\"<ID_anonymized>\",\"resourceType\":\"Item\"}}"
}
]"This suggests that when pagination is enabled, the Copy Data activity does not gracefully handle references to deleted items, causing the pipeline to fail. When pagination is removed, the initial data is returned successfully.
My question is:
What is the recommended way to handle or mitigate this scenario?
Is there a way to ignore deleted items, add error handling, or configure pagination so that the pipeline does not fail when encountering a deleted resource?Any guidance or best practices would be greatly appreciated.
Thanks!
collinq ,
Following up on my previous message, I’ve discovered some new information about this error.
After further testing, the issue seems to be specific to APP-type artifacts. When I call the API and explicitly request other artifact types, the request runs successfully without any issues.
Based on the tests I’ve performed so far, only APP artifacts return the error mentioned earlier. This suggests the problem may be isolated to how APP artifacts are being handled by the Admin Items API.
Just wanted to share this additional finding in case it helps with the investigation.
Thanks!
15 Replies
I confirm, the issue has been fixed yesterday. Thanks!
Hi everyone,
I’m experiencing the same issue, and it started today as well.
I suspect this is specifically related to the pagination rules configured in the Copy Data activity. In my pipeline, when pagination is enabled in the Copy Data activity, the API call fails or does not return the expected results. However, as soon as I remove the pagination rules from the Copy Data activity, the pipeline is able to retrieve the initial data successfully.This makes me think there may be a problem with how pagination is being handled (or enforced) on the API side, possibly due to a recent change.
Has anyone else noticed similar behavior or found a workaround?
Thanks!
Hi brsantos ,
I found this:Copy Activity pagination is client‑driven
When you enable pagination rules in Copy Data (REST source), ADF/Fabric:Sends the first request
Reads the pagination token / URL from the response
Constructs the next request exactly as configured
Stops immediately if:the token path doesn’t resolve
the token format changes
the API returns a value the rule can’t parseIf you remove pagination rules, ADF:
Executes only the first request
Successfully returns the initial page (which matches your observation)This is expected behavior, not a partial success.
So, I would think then that you would check those Stops immediately issues to see if that is affecting you.
collinq ,
Following up on my previous message, I’ve discovered some new information about this error.
After further testing, the issue seems to be specific to APP-type artifacts. When I call the API and explicitly request other artifact types, the request runs successfully without any issues.
Based on the tests I’ve performed so far, only APP artifacts return the error mentioned earlier. This suggests the problem may be isolated to how APP artifacts are being handled by the Admin Items API.
Just wanted to share this additional finding in case it helps with the investigation.
Thanks!
Hi VOLBE ,
I would also like to take a moment to thank brsantos for actively participating and sharing valuable insights on this thread, your contributions are truly appreciated.
VOLBE could you please confirm if you had a chance to review the information shared.
Let us know if it helped or if you need any further assistance.
We are happy to help.I am still experiencing this issue. Removing pagination doesn't work for me, as I have more than 10k items in my tenant. Can the Fabric items API be rolled back to previous version?
marvas I tested a palliative solution at my company.
In my case, I have a data pipeline with a Copy Data activity that points to the Items API as the source.
I added a For Each activity on top of that Copy Data activity so we can loop through the item types (I included a variable with the types, excluding the APP type).
That way, I didn’t encounter any errors.
Note: You can pass a specific item type in the relative URL like this:
items?type=report
Hi VOLBE ,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you
