What is the jobId in the triggerWorkflow result?

[chrisli30]

What is the jobId in this response of triggerWorkflow? Could you write the explanation here so I can include it in the sdk?

It’s generated from one of the triggerWorkflow test cases.
AvaProtocol/ava-sdk-js#45

{ result: true, executionId: '', jobId: '4' }

[v9n]

@chrisli30 > Could you write the explanation here so I can include it in the sdk?

It's an internal job of that execution in the worker queue. Right now, client cannot do anything with it yet but maybe in the furure.

[chrisli30]

What’s the relationship between the executionId and the jobId?

Is jobId sub-tasks of an execution, and starts from 0?

[v9n]

@chrisli30

What’s the relationship between the executionId and the jobId?

there is no direct relationship currently.

Is jobId sub-tasks of an execution, and starts from 0?

no, it isn't

It is just simply an ID of an internal queue system that used to run these job. When a job is run async, they are enqueue to be run. That's the internal id in that queue. A worker pop the work from that queue to run.

I'm going to remove this field to avid any confusion about its usage or id. So when run a job is trigger in async manner. Sound good to you?

[chrisli30]

okay, so sounds like it’s for internal use only? If that’s the case, let’s remove it from the API response.