SIMPLE tasks remain in SCHEDULED status after upgrade to v3.21.16 (PostgreSQL queue)

[albert-cg]

Describe the bug
After upgrade Conductor OSS from v3.21.14 to v3.21.16, during testing, I noticed that SIMPLE tasks remain in SCHEDULED status in the UI and in the database, even though the worker logs show that the task is being executed (IN_PROGRESS). Also I send heartbeats and I captured the heartbeat output in UI but tasks stills in SCHEDULED.

Details
Conductor version: v3.21.16
Conductor worker version: 1.10.1 and 1.2.2
Persistence implementation: Postgres
Queue implementation: Postgres
Lock: N/A
Workflow definition: Any
Task definition: Any
Event handler definition: N/A

To Reproduce
Steps to reproduce the behavior:

1. Launch workflow with SIMPLE task
2. See task as SCHEDULED
3. See logs as worker doing task and see output in the heartbeat

I've added to the worker get the status of the task id and return SCHEDULED.
Logs snippet showing heartbeat and update_task(IN_PROGRESS):

INFO - [task_name] - Sent IN_PROGRESS status
INFO - [task_name] - update_task(IN_PROGRESS) response: 155f253d-fe58-479c-95dc-e124e5aff67a
INFO - [task_name] - Server state after IN_PROGRESS: SCHEDULED

Database entry

"status":"SCHEDULED",
"callbackFromWorker":true,
"workerId":"conductor-worker-python-poc-59dcdff45-5hd8k",
"outputData":{"heartbeat":"Task started and marked as IN_PROGRESS"}

Expected behavior
Task should be marked as IN_PROGRESS

Additional context
Can be related with this MR:

• Introduce Signal API and SYNC-DURABLE consisteny during execution #481

[nthmost-orkes]

Hi @albert-cg sorry for the delay, i'm just looking into this now. Thanks!