With the "Jedox Instance Synchronization" feature, users can copy information from one instance to another, including the scheduler. https://knowledgebase.jedox.com/jedox/maintenance/synchronization.htm
After copying from the test environment to the live environment, the problem arises when the scheduler in the test environment remains active and continues running.
It would be beneficial if a mechanism were implemented to determine whether a job is executed in the test or live environment. If it's identified as being in the test environment, the scheduled job should be automatically canceled.
To be more precise, it's crucial to make decisions not only at the scheduler level, but ideally for individual jobs as well.
While certain daily jobs must continue to run to maintain the environment's currency, others should be deactivated, especially those that load external SQL tables, as this is not desirable when working with test data.
