HTTP Task remains in scheduled state

[autodidactic]

The workflow created from conductor UI using new workflow definition button creates a basic workflow with default HTTP task called get_population_data
The workflow remains in running state and http task is scheduled. I expect it to go to complete while skipping running , almost immiediately. but not the behaviour i see in 3.13.5

it remains in scheduled state

here is the json

{
"createTime": 1680633455822,
"name": "Conduc_3.13.5",
"description": "conductor workflow for 3.13.5",
"version": 1,
"tasks": [
{
"name": "get_population_data",
"taskReferenceName": "get_population_data",
"inputParameters": {
"http_request": {
"uri": "https://datausa.io/api/data?drilldowns=Nation&measures=Population",
"method": "GET"
}
},
"type": "HTTP",
"startDelay": 0,
"optional": false,
"asyncComplete": false
}
],
"inputParameters": [],
"outputParameters": {
"data": "${get_population_data.output.response.body.data}",
"source": "${get_population_data.output.response.body.source}"
},
"schemaVersion": 2,
"restartable": true,
"workflowStatusListenerEnabled": false,
"ownerEmail": "[email protected]",
"timeoutPolicy": "ALERT_ONLY",
"timeoutSeconds": 0,
"variables": {},
"inputTemplate": {}
}

steps to reproduce:

connect to conductor ui
click on definition
click blue button "new workflow definition"
enter name or workflow and desc and other mandatory fields
save it

click on workbench and select the newly created workflow
execute workflow
navigate to executions screen and wait for workflow to show up
verify status is running and task is scheduled

i do not see task in HTTP task queue
i do not have invisible duration

we are using mysql not postgres for persistence. is there an issue with dyno queues not popping duplicate elements?
any help or update would help us decide on how to proceed on this version or wait for fix