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

WorkflowTaskTimedOut Issue

Open
#316 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

No file, test, or entry point is named. Start by reproducing a WorkflowTaskTimedOut followed by cron scheduling and compare the task queue with the queue used when no timeout occurs. Done means the cron task queue remains the configured queue in both cases, with a regression test covering the timeout path.

Written by the indexing model from the issue text.

Description

After the WorkflowTaskTimedOut i can see Cron is scheduled with default task queue which is temporal-sys-per-ns-tq in my case, but without any timeout issue cron got is getting scheduled with proper defined queue name

Dominant language
Ruby
Stars
287
Forks
113
PR merge metrics
No merged PRs in 30d

Getting set up

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 coinbase/temporal-ruby

All issues in coinbase/temporal-ruby

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.