Pipelines: Controller is not valid

[Bradley Marin]

We recently cloned over the instance that I am trying to setup this environment record on. This is the controller instance, and I am attempting to setup the environment record for this instance. When I attempt to validate the record, I get a "Controller is not valid" error. This only started happening after the clone. 

Just wondering if anyone else has experience this type of behavior after a clone and if there are any known solutions. 

[Peter Bodelier]

My first guess would be that you need to validate the credentials you're using in the Environment record, to ensure it gives access to the instance. (Even if the instance is itself)

[Bradley Marin]

Hi, 

That is what I am trying to do but when I do I get the "Controller not valid" error. 

[Peter Bodelier]

Do you have ip filtering or some other way of access control implemented?

If not, I would suggest to create a case at Now Support to get help.

[Bradley Marin · Accepted solution]

I ended up just deleting the controller environment record and re-creating it. That solved the issue. This is not the first time I've encountered this though so might need some input from ServiceNow themselves.