Forum Discussion
https://api.fabric.microsoft.com/v1/admin/items REST API does not work
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!
Advocate IHi everyone,
I’m experiencing the same issue, and it started today as well.
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!
- collinq
Super User
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.
- brsantos
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!
- brsantos
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!
I recently received this error as well. After some intense digging, I also noticed it targeting apps. I actually was able to delete the first app that it was triggering on since it was orphaned but then came across an app we were actually using when the error came up again. But deleting the apps it was targeting seemed to progress to the next app.
I think this is a Microsoft fabric api issue targeting just apps and needs to be resolved on Microsoft's end.
I just removed the pagination. It won't matter unless you have more than 10k items on your tenant.
