App Engine Studio Pipelines and depolyments

[Karen47]

We re trying to set up App engine, we installed the production in our dev instance, and is trying to create pipelines to test and production, we were able to create a pipeline to production however, when we try to create one to test we are getting the below error message.

Could not connect to the environment. [Method failed: (/api/sn_pipeline/pipeline/validate_connection) with code: 400]

Any suggestions as to what is going on?

Thanks, Karen

[HrishabhKumar]

Hi @Karen47 ,

Check the following:

• Check Connection Details:

  • Ensure that the connection details (URL, credentials, etc.) for the test environment are correct.
  • Verify that the test environment is accessible from your dev instance network.

• Network and Firewall Settings:

  • Make sure that the necessary network ports are open between your dev instance and the test environment.
  • Check if there are any firewall rules that might be blocking the connection.

• ServiceNow Permissions:

  • Ensure that the user account being used for the connection has the necessary permissions in the test environment.
  • Verify that the user has the appropriate roles for pipeline creation and management.

• Pipeline Configuration:

  • Double-check the pipeline configuration settings for any discrepancies or errors.
  • Ensure that the correct environment type is selected (e.g., Test vs. Production).

• Instance Status and Health:

  • Check the status and health of the test environment instance. Ensure it is up and running without any issues.

• API and Integration Logs:

  • Review the API and integration logs in both the dev and test environments for any error messages or hints.
  • Look for any failed API calls or detailed error messages that might provide more context.

• Validate Connection Endpoint:

  • The error mentions the /api/sn_pipeline/pipeline/validate_connection endpoint. Ensure that this API endpoint is correctly configured and accessible in the test environment.

Thanks,

Hope this helps.

If my response turns helpful, mark it helpful and accept solution.

[RM313]

Hi @Karen47 ,

Did you happen to resolve your issue? Im having the same experience on my end. 

Thanks!

[Karen47]

No this did not resolve the problem

[WORKFLOW-COWBOY]

This is usually caused by the Instance credential not having the right password to make the connections. Or it is that the credential does not have the 'admin' role on the target instance. 

--------------------------------------------------
If my response proves useful, please indicate its helpfulness by selecting "Accept as Solution" and " Helpful." This action benefits both the community and me.

Thanks!