Hi guys,
I’ve been ravaging again through the OL Connect REST API Cookbook reference (Welcome) but cannot see any way to pause a process/job. I’m not sure if this is even possible with the current state of planetpress connect. There is the cancel an operation but not pause/resume an operation. Is this something that can be added?
Thank you in advance.
James.
That is correct, this is not something that is supported at the moment. Why would you want to do that, what are your use cases for this feature?
My use case is if I have a large job that would take a long time to process and another smaller job where in terms of urgency the smaller job is required to be run first. But already the large jobs is already running. Then pausing the current long running job to quickly run a smaller job would be ideal. There are the settings on the OL Connect Server Configuration on Parallel Processing which I can utilize, but thought if this was something which could be achieved. Whether it being possible or not I’m not sure. Maybe someone in the forum could chime in for other use cases.
This shouldn’t be necessary. Connect has extensive customization options regarding how jobs are scheduled. I suggest that you have a look at the Parallel Processing page in the Server Configuration application. You can find the documentation here: Parallel Processing preferences.
You could instruct your service to not execute the next step, not exactly a pause but still a mechanism to interrupt a flow.
For instance if you have a big datamining followed by a big content creation you could prevent your system to call the content creation api. However, you will need to ensure that temporary data is not lost according to cleanup schedules.
Thank you @Maxiride,
I may invest more time to your suggested solution as I already use the all-in-one process in running jobs. But still would be nice to have a Pause an Operation REST endpoint feature similar to the Cancel an Operation which we currently have.
… or use the built-in scheduling features which allow to cover this exact use case, i.e. make smaller jobs pass in front of bigger ones. The On Demand Print scenario appears to be the most appropriate, and may be tweaked if necessary.
Thank @fortiny, but how hard is it to add this feature? " Pause an Operation REST endpoint"
The amount of work required to implement this is unkown at this time because it hasn’t been analyzed yet. But considering that this would introduce a new behavior in a critical portion of the Connect Server core, my guess is that it isn’t a trivial task.