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

[RM313]

Thanks for the info. I deleted the credentials, recreated with the same user and password as PROD and still unable to validate my dev instance. I verified the account I am using has admin role. Anything else I should check?

[WORKFLOW-COWBOY]

ServiceNow has a great App Engine Studio - System Administrator Guide available on Now Create that gets updated every release. 

From the guide:
It is recommended to use a username/password for a service account so that the password does not expire or change. The account must exist in the target instance(s) and have admin permissions.

Are you able to log in from your browser to the target environment using the login and password that you are storing in the credentials? 

Link to Guide on Now Create

https://nowlearning.servicenow.com/nowcreate?id=nc_asset&asset_id=9eb4a83887f2c650f2f443f7dabb3548&n...

[Sandesh Kadam]

Are you specifying correct Instance ID? I faced similar issue when I used incorrect Instance ID.

Moreover just make sure you are propagating credentials and Connection Alias by Import/Export XML between instances. 

[WORKFLOW-COWBOY]

It is possible to manually get the Instance ID from the stats.do page on the target instance; however, if the credentials are not working, then the pipeline will still not function correctly. 

[RM313]

Hi All, 

I appreciate the suggestions. I have resolved the issue and the solution was redoing the credentials. I have used the same credentials for all instances. 

For anyone else having this issue, either create credentials that are the same in all instances or create separate credentials alias for all environments in production instance. Make sure the account you are using has admin rights and test by trying to manually login to that instance with the credentials.