Cloud customers: How do you prevent your scheduled reports/processes in the System Agent from running in Pilot after the cloud team restores your Pilot environment from Live?
For example, if the cloud team finishes the restore of Live to Pilot at 2:00 AM and we don’t get in until 7:00 AM, there’s 5 hours of various reports being emailed out and processes running TWICE (once in Live and once in Pilot).
Thanks for any ideas you might have for us!
1 Like
If they’re scheduled, that means they’re usually tied to a “Schedule” In System Agent Maintenance.
You can look in there and disable schedules if you don’t want them running.
Yes, I’m aware of how to disable schedules in System Agent. My question is about the in between time. The time between whenever the cloud team finishes the restore and the time we are able to get in and disable schedules in the restored environment. During that “in between time”, all schedules would be executed in both Live and Pilot.
2 Likes
Oh, I gotcha. Apologies.
I don’t know if you could make that part of your “restore” request to EpiCare? Perhaps they can disable all agent schedules after the restore for you.
I’ve seen several posts from people talking about requesting various things of EpiCare and I’m always thinking, “Oh, I never knew we could ask for that!”
Certainly wouldn’t hurt to try.
1 Like
I would make the support team aware. We do not see that behavior on our refreshes because they disable the schedules. I believe that is supposed to be part of their refresh process.
3 Likes
I just had ours refreshed last week and the schedules were still enabled. Can’t say I’ve paid too much attention in the past as we didn’t have reports scheduled until recently. Just scheduled tasks like generating suggestions, etc.
That being said… the Schedules are still enabled… but I don’t see any “scheduled tasks” in the System Monitor. So, they must be disabling those via a different path??
I wonder if we could have a scheduled function that runs at start up that checks the local environment and then disables tasks if it is not the production instance. While we’re at it, we can update the Production Flag, so other BPMs can avoid emails, etc.
5 Likes
Interesting, our the scheduled tasks are completely removed after refreshes. We are public gov cloud customer so not sure if that makes a difference. Sounds like there is not consistency in the process by support.
2 Likes
Wishlist - also clock out employees.
3 Likes
I’m pretty sure mine have always been disabled as well, but I do like @Mark_Wonsil ‘s idea about the startup function, just in case.
If they are still enabled, then it would run and turn them off. If not, well you don’t have a problem.
3 Likes
On-prem, I had a big red button in company maintenance that was only enabled for non-prod. On click, It would disable all function/directive emails, remove all scheduled tasks, remove all live task agent service definitions, and disable APR. I wish i still had the code to share here
4 Likes
On prem as well. When I restore a backed up database, my script goes in and assigns all sorts of settings to handle these as well. Since it’s not a production server, I have no issues updating/deleting at will!
2 Likes
So in the past, the cloud team has always completely deleted our scheduled tasks. Despite many complaints about this (makes it hard to test MRP etc) they insisted there was no alternative (why can’t they just disable everything? Its literally the same amount of work assuming you are using a script?). I even had an epicor idea on this that got rejected.
But on our last restore, they did not delete OR disable the tasks and everything was left running much to my surprise. This of course is also problematic.
I would complain except its impossible to get a straight answer about literally anything with the cloud team. I don’t know if they have new people who were not trained on a process, somebody is just forgetting a step, or they changed their process and didn’t tell anyone?
5 Likes
KB0119590 has some info 
Not too helpful for cloud, but OnPrem, I have a restore script that in addition to restoring UAT from PROD, also changes the company names (with a date stamp so we always know last refresh), disables all of our APR routing rules, and a few other BPMs, changes the QuickShip endpoints, and one or two other things I am most likely forgetting (which is why I scripted them).
1 Like
Yes that was always the process in the past. Like I said it was not done on our most recent restore and I have no idea if it was a mistake or a process change.
I wonder if their new portal will let us kick off a refresh, wishful thinking probably.
1 Like
It does, but I don’t know if any restrictions will be placed on their initial rollout.
@bderuvo, @Evan_Purdy , what did they say in y’all’s meeting?
2 Likes
I signed an NDA.
2 Likes
Can be done with Functions in the cloud too…
1 Like