Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Retry messages are lost

Open
#72 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

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.

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
Dominant language
TypeScript
Stars
58
Forks
20
Avg merge
6d 5h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from conductor-oss/javascript-sdk

All issues in conductor-oss/javascript-sdk

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.