mnmnc

It does not work for you probably due to permissions error on the service configuration file, or wrong service configuration - maybe you have relative path in the service configuration?...

@wloody54 your query in curl is wrong. Look at the example in code: 

I think no_proxy is system level variable. Not really handled by requests directly. Maybe you can supply proxies variable only to the calls that you want proxied.

GUI certainly has the option to create a case.  I found that the best idea is to setup docker + docker compose environment and use one of the templates...

I don't have a solution but a suggestion for further investigation to narrow down the cause: Change API limit to `2` and see if it executes `4`. If so then...

Are you sure they disappear? Remember that depending on cache value if you run a job for a value that is in cache, the new job will not be created....