conductor-oss / conductor-oss/javascript-sdk

Retry messages are lost

Open
#72 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
58
Forks
20
Avg merge
1d 13h
Merged PRs (30d)
7

Description

I have a workflow execution with dynamic fork and the first time the workflow executes, the tasks are polled by the worker and the workflow runs to execution.

Image
Image

If the first execution of the task is failed manually via UI, the retry tasks are created and they are visible in the queue. These retry tasks queue becomes empty the moment the worker is started and the worker polls no task and the workflow does not move forward.

Image
Image
Image
Image

Contributor guide

No contributing guide indexed for this repository

Research direction

No files or tests are named. Reproduce the dynamic-fork workflow, manually fail the first task through the UI, then inspect the worker polling and retry-task queue path; done means retry tasks are consumed and the workflow advances.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.