Pipeline Debug not working in ADF

Question

Hi all,
I am having trouble debugging the ADF pipelines in Stage environment, namely, if I click "Debug" button to check if everything is ok with the ETL process, it is failing with the following error message below
"Error: Unable to save [adf-instance-name]. Bad resource".

But luckily, the "Trigger" button is working. I am now testing the pipeline by triggering it.
The scheduled pipelines are also working well.

Anyone have any idea what's happening here?

PS: This started happening after I promoted my Dev ADF environment to Stage using ARM templates manually.
But interestingly, I also promoted the same Dev to Prod ADF and nothing bad has happened yet to Prod. Dev and Prod ADFs are now working smoothly.

I must also say that the scheduled ADF pipelines in Stage are also working. But still, the Debug feature would be needed during work for testing. By the way, data previews inside Mapping Data Flows are not affected, they are working properly, at least.

Any help would be appreciated
Thank you!

Answer 1

Did you verify if all linked services in the Stage environment have the correct credentials or authentication settings ?

If all configurations look correct, try:

• Restarting the IR in Stage.
• Re-publishing all pipelines in the Stage environment.
• Redeploying the ARM template with a focus on resource dependencies.

https://learn.microsoft.com/en-us/answers/questions/1247709/i-am-getting-a-badrequest-error-while-running-adf

https://stackoverflow.com/questions/74449644/upon-cicd-pipeline-deployment-to-another-environment-i-get-a-bad-resource-error

Answer 2

@Nodir Sadullaev

Welcome to the Microsoft Q&A forum

Please Check the below steps and let us know

Check Resource Limits: Ensure that your ADF instance in the Stage environment isn't hitting any resource limits. Sometimes, resource constraints can cause such errors.

Validate ARM Templates: Since the issue started after promoting your Dev environment to Stage using ARM templates, double-check the templates for any discrepancies or missing configurations. Ensure that all resources and dependencies are correctly defined.

Integration Runtime: Verify that the integration runtime (IR) settings are correctly configured in the Stage environment. Sometimes, issues with the IR can cause problems during debugging

Pipeline Configuration: Review the pipeline configuration in the Stage environment. Ensure that all parameters, connections, and activities are correctly set up. Pay special attention to any differences between the Dev and Stage configurations

Permissions and Access: Ensure that the ADF instance in the Stage environment has the necessary permissions to access all required resources. Sometimes, permission issues can cause such errors.

Logs and Diagnostics: Check the ADF logs and diagnostics for more detailed error messages. These logs can provide additional insights into what might be causing the issue

Recreate Pipeline: If the issue persists, consider recreating the pipeline in the Stage environment. Sometimes, recreating the pipeline from scratch can resolve underlying issues

I hope the above steps will resolve the issue, please do let us know if issue persists. Thank you