Hi, I would like to ask for some clarification regarding minions and using the rest API to execute a task (segmentGeneration) When I have no minions started and I try to execute a task, the task shows up in as

"Task_SegmentGenerationAndPushTask_smth_f11b81f0-cc0f-4c8d-b205-4873963f49d4": "IN_PROGRESS"

when calling

GET /tasks/SegmentGenerationAndPushTask/state

, but when checking with

GET tasks/subtask/Task_SegmentGenerationAndPushTask_smth_f11b81f0-cc0f-4c8d-b205-4873963f49d4/state

I get

{
  "Task_SegmentGenerationAndPushTask_smth_f11b81f0-cc0f-4c8d-b205-4873963f49d4_0": null
}

The controller logs clearly states

2025/10/10 11:04:55.086 ERROR [JobDispatcher] [HelixController-pipeline-task-smth-(2c58d6d3_TASK)] No available instance found for job: TaskQueue_SegmentGenerationAndPushTask_Task_SegmentGenerationAndPushTask_smth_f11b81f0-cc0f-4c8d-b205-4873963f49d4

I was expecting that the status of the task to also reflect that by showing

"NOT_STARTED"

.

Do you have minion instances running? scheduling a task doesn’t provision minion instances, it just uses existing ones.

In this scenario I specifically shut my minions down

Yea that seems like a bug cc @Shounak Kulkarni

IN_PROGRESS is set by helix . Looks like adhoc/execute call somehow invokes the helix workflow processing that sets this initial state. Whereas with scheduled/cron flow, it'll start with NOT_STARTED. When the task is set by cron/it'll probably marked NOT_STARTED because scheduled has not kicked in yet. Need to check.

any updates to this issue ?

Is this blocking ?