Encountering 'Bad Request' Error Whenever Debugging Azure Simple Pipeline

Question

I am trying to debug a simple Azure pipeline, but I consistently encounter the following error:

"code": "BadRequest", "message": null, "target": "pipeline//runid/94168fdf-d49b-4ca8-9d01-dc17298b4b5d", "details": null, "error": null

The error seems to indicate a 'Bad Request', but the exact cause is unclear. I am passing two string parameters, "triggerStartTime" and "triggerEndTime", which are essential for capturing changes from the source database to my blob storage. My connections to both the source database and blob storage are functioning correctly.

Please note that my pipeline's name and my activities' names don't contain any whitespace or any special character.

Could this be a bug in Azure? What steps can be taken to resolve this issue? Any assistance would be appreciated.

Answer 1

Hi @PHẠM NGỌC THÙY TRANG
Welcome to Microsoft Q&A platform and thanks for posting your query here.

Based on your error encountering ("BadRequest") might be caused by several factors, and it's important to check the pipeline configuration and input parameters closely.

Here are some steps you can try to resolve the issue:

• Check Parameters: You are passing two parameters: triggerStartTime and triggerEndTime. Ensure that the values for these parameters are correctly formatted. If they are date/time values, verify that they match the expected format for the pipeline activity. It’s also a good idea to check if these parameters are being correctly passed and handled within the pipeline.
• Try running the pipeline without parameters: Try running the pipeline without passing any parameters to see if it runs successfully. If it does, then the issue might be with the parameter values.
• Check Activity and Dataset Configuration: Double-check that the dataset and the activities you are using (such as the Lookup activity and Copy activity) are properly configured. Also, ensure the dataset source and sink are correctly linked to the activities and parameters.
• Check the pipeline activity logs: Check the activity logs for your pipeline to see if there are any errors or warnings that might be causing the 'Bad Request' error.
• Validate JSON Payload: If your pipeline involves JSON payloads, ensure that they are correctly formatted and valid. Sometimes, a small syntax error can lead to a ‘Bad Request’ error.
• Check the ADF integration runtime settings. Make sure that the integration runtime settings are correct and that they are not causing any issues. For example, check the network settings, authentication settings, and performance settings.

If none of these step's work, you can try recreating the entire ADF pipeline from scratch. Sometimes, recreating the activity or pipeline can resolve any underlying issues.

For common bad request errors watch this video for more information.

I hope this helps you troubleshoot and resolve the BadRequest error in your ADF pipeline. If you have any further questions or concerns, please let me know.