Forum Discussion
Errors like 403,404 while running FUAM pipelines
Hello Shreya_Barhate
Since the child pipelines run successfully when you run them interactively, it suggests to me that it is related to API authorization on the identity runnig it. When you run a pipeline directly, the REST APIs execute under your identity context, and you may have all the required authorization - hence they succeed!
When the E2E pipeline orchestrates it, it is using the connection identity, which is probably lacking the Admin API access in tenant settings.
There could also be a case of concurrency, since you mention that not all errors are consistent. This is probably because the Admin APIs are throttled, and you're hitting those limits.
I suggest you use the following:
- a service principal enabled with admin API setting for running the pipelines
- try running child pipelines sequentially or with a low batchcount, with retries
Hi Shreya_Barhate,
Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to the deborshi_nag for sharing valuable insights.
Could you please confirm if your issue has been resolved using the suggested approach? This will help other community members facing similar scenarios.
Thank you.
hi v-shchada-msft , deborshi_nag ,
Thanks for your response. Interestingly, the pipeline completed successfully later without any changes, so I’m trying to understand what caused the inconsistency in the earlier run(s).
I’m running the pipelines via a service principal with the necessary Admin API settings enabled. Are there known intermittent issues with this approach, or could you suggest which telemetry/logs/settings I should validate to narrow this down?
But for now issue is solved.
Thanks,
ShreyaGlad to know the pipeline completed successfully. Try to reduce the concurrency gradually and see if that reduces the occurances of these failures.
