I am using Pega DM (5.6.1) to run Run Pipeline (Azure Devops) . Configuration is made as described in the document : Configure an environment to call Azure DevOps (pega.com)
I get 400 error and error message does not give any info. How do i debug this. Where can I find the response from Azure Devops.
Can you please help me
@ShameemV16612309 To debug the 400 error and find the response from Azure DevOps you can follow these steps: 1. Check the Diagnostic Results: Run diagnostics on your pipeline to assess whether it is healthy and correctly configured. The diagnostic results can help identify configuration and connection issues. You can refer to the error messages from the diagnostic check to understand the best way to troubleshoot them. For more details you can refer to the documentation on running and troubleshooting diagnostic errors on pipelines. 2. Review the Configuration: Ensure that the configuration details such as the pdm callback routine.yml file pyID Pega Orchestrator URL Client ID and Client secret are correctly embedded and saved. Verify that the full path of the template is provided in your main pipeline. 3. Check Environment Connectivity: Ensure that the environment configured on the pipeline has PegaDevOpsFoundation (6.1.3 or later) and that the environment connectivity status is available from Resources Environments. 4. Review Logs: Check the logs for any detailed error messages or responses from Azure DevOps. This can provide more insight into what might be causing the 400 error. If the issue persists you may need to contact Pega Support for further assistance.
This is a GenAI-powered tool. All generated answers require validation against the provided references.
@MarijeSchillern Currently , I have configured any call back. I am only interested just triggering the Azure Tests. Call back will be my next step.
In first step after configuring the parameter and triggering the pipeline to Run Azure Taks gives me 400 error.
Run diagnostics on my pipeline is working fine without any errors.
@ShameemV16612309 as stated If the issue persists you may need to contact Pega Support for further assistance.
Please log an INC via the MSP and provide the INC id here so that we can help track it.