REST API: Priority Parameter in TaskExecutionConfig

[MikeW]

Does higher number gets higher priority or does lower number gets higher priority? 

https://help.qlik.com/en-US/nprinting/November2019/APIs/NP+API/index.html?page=109 

Thanks

[Lech_Miszkiewicz]

judging by my observation all metadata generation tasks get 1000 priority, and publish tasks 500... I would assume higher number gets priority. 

I am not sure however what do you need this information for as API does not allow you to set it. It only allows you to get it (similar to what you see in task overview).

thanks

Lech

[MikeW]

The POST /tasks/{taskid}/executions  takes this config as an optional request body. 

I was able to pass it as a parameter when executing the POST call and can see the specified priority in the execution status. I ran it a bunch of times, but I didn't have enough server load to see any difference in how fast NPrinting got to my task. 

Here is the call I used.

		RestNPTaskTriggerTable:
		SQL SELECT
    		"__KEY_data",
    		"id",
    		"task",
    		"status"
		FROM JSON (wrap off) "data" PK "__KEY_data"
		WITH CONNECTION( 
        	URL "$(vEndpoint)", 
            HTTPHEADER "cookie" "$(vCookie)",
			HTTPHEADER "Origin" "$(vL.NPAPIOrigin)",
			HTTPHEADER "Content-Type" "application/json;charset=UTF-8",
			BODY "{""priority"":1000}"
        );

[Lech_Miszkiewicz]

hi @MikeW ,you are right,

let me play with it and check if there is any usability of this parameter

cheers

LEch

[Ruggero_Piccoli · Accepted solution]

Hi,

1000 is the maximum priority. There are other optimization rules that determine the execution sequence and I don't know if we will made them public. In any case you can set API execution requests to 1000 to give them the maximum possible priority.

Best Regards,

Ruggero