There are some use cases that user want to pause the scheduled operation (not schedule it from now), and then some time later he will resume it again (schedule it again). So in order to support this cases, we can add two APIs, one is pause and another is resume.
Based on the designs of Operation Engine, we can implement them by following steps separately.
1. pause
unregister the scheduled operation which is registered to some trigger;
change the state of scheduled operation to 'paused' in the DB
2. resume
register the scheduled operation to the trigger
change the state of scheduled operation to 'triggered' in the DB
There are some use cases that user want to pause the scheduled operation (not schedule it from now), and then some time later he will resume it again (schedule it again). So in order to support this cases, we can add two APIs, one is pause and another is resume.
Based on the designs of Operation Engine, we can implement them by following steps separately.
1. pause
unregister the scheduled operation which is registered to some trigger;
change the state of scheduled operation to 'paused' in the DB
2. resume
register the scheduled operation to the trigger
change the state of scheduled operation to 'triggered' in the DB