Check Progress of a Job in V2024.2

OL Connect Professional
1

Hi

Before V2024.2 we used to be able to put the below URL in on our pres server and we could see what was running and what percentage it was running at:

http:''localhost:9340/rest/serverengine/workflow/outputcreation/getOperations

However we are just trailing V2024.2 and noticed that after a while you just get a response of

{“error”:{“status”:500,“message”:“Request failed.”,“parameter”:“”}}

If you reboot the server it works again but after a while it stops again. Does anyone know any other way of seeing what’s running and how far along it is?

2

Hello @jbeal84,

Sounds like the 500 error that you reported in the past (#1655731). Could you submit a new support ticket via our support portal for this please?

P.S. Can you also please edit your forum post and make sure that the shared link is not clickable? You can do this by removing the link from your post and by adding it again to the post but place it between two single backticks (`) instead. Otherwise, people may click on it my mistake. :slight_smile:

3

Hi Marten

Yes it is the same error, however the new code you gave me for my tickets is working fine so must not be using this URL anymore I guess? I’ll raise the ticket now

1 Like
4

Internal reference: #1677929

5

Update: This issue has been reported to R&D and occurs when thousands of requests have been submitted [internal reference: SHARED-94723]. The workaround for the moment is to add an extra header to the request just after the function open()–For example, xmlHttp.open()–when the error occurs when executing a REST API call by the Run Script Workflow plugin and JScript is chosen as Language.

xmlHttp.setRequestHeader("Authorization", "Basic <Base64>");

Tip: The value <Base64> is the base64 string of username:password (colon incl.). In case of username:password, this value would be dXNlcm5hbWU6cGFzc3dvcmQ=.

6

Hi @jbeal84 ,

Sorry to bother you have you got a solution to your issue?

I seem to be getting same error result when using the REST Api especially on big requests.
The only workaround for me atm is to restart Connect Service.

Thanks in advanced.
Kind regards
Ernani