Automated cleanup of scheduled jobs/mail notifications in DR instance post-EPBCS environment cloning
In our EPBCS application, we use the cloneEnvironment command as part of a daily automation to refresh our Disaster Recovery (DR) environment from Production. This clones the entire environment, including scheduled jobs.
The challenge we’re facing is that the scheduled jobs (Pipelines) from Production are also brought into the DR instance during the clone. These jobs begin executing in DR and trigger email notifications to business users, which is not ideal in a non-production environment.
We are exploring options to clean up or suppress these scheduled activities in the DR instance via automation. Specifically, we’re looking into whether it is possible to:
Tagged:
0