Question on "/rest/serverengine/workflow/print/getOperations"

OL Connect Professional
1

Hi All,

I’m hoping someone can help clarify something, as I’m not sure if I’m misunderstanding what I’m seeing.

I’m running jobs daily via the API, and occasionally I notice one or two additional jobs appearing in the list after they have completely run. These jobs seem to appear briefly and then disappear on their own when I run another job(s). If I quickly select one of them and cancel it, it is immediately removed from the list.

The endpoint I’m querying is:

/rest/serverengine/workflow/print/getOperations

Has anyone experienced something similar, or can explain why this might be happening?

Thanks in advance.

2

Hello James,

The reason why this is happening is because jobs with a operation progress value of 100, followed by the value of ‘done’ on completion, also appear in the list – See Get Progress of Operation - OL Connect 2025.2 API Cookbook.

3

Hi Marten,

The job(s) being returned should be removed when their status are progress=100 and followed by ‘done’, isn’t it? They should not be visible is they are complete. That is my understading. Its a job(s) that were ran a long time ago and completed, but still showing up. Its like a ghost job is hauting the server processes.

Why the jobs still appear even though they finished/completed long time ago?

4

The following could be the reason why:

5

Ahh, I see thanks for the explanation.

However, I am already calling Get Results of Operation to retrieve the absolute paths of the output files (or the file content itself), which successfully returns the results I need.

If I attempt to call Get Results of Operation a second time for the same operation, I receive a 404/error response, as the result has already been retrieved.

Given that, I’m unsure why the operation would still appear in the list intermittently.