This is working has designed and has been implemented throughout other areas of the system.
This is in place so that the play system doesn't inadvertently update the live system of an integrated application with test data.
If you would like to re-connect to the Orchestrate system, you will have to re-enter the connection details, but you have the potential of multiple systems inputting records into the Live Orchestrate system.
The issue is that there is no way of the system knowing the difference between not having the Orchestrate enabled and no details entered due to user error or copy live to play.
The intention of the check is to tell if the system cannot connect to Orchestrate and it has been defined as the scheduling program.
The error is skippable, you can click cancel without any consequences.
There is a idea raised on the ideas portal to improve this functionality. Please vote for this idea and our Product and Development team's will assess this idea for future implementations of Factory Master.
Lose Orchestrate connection setting after running copy live to play
I update to a new version and the finalise update fails as these settings are not in place. You have to then go in and reconnect to the Orch Play database in the settings and then run the finalise update again.
Written by Jes
Updated over 2 months ago