Spec 9: world-vercel step listing stays stale for over 30s after a run completes

Open
#5,605 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
backend, testing

Research direction

Start with stepsOf in packages/core/e2e/e2e.test.ts and the spec 9 README section “Steps on world-vercel”; compare world.steps.list() and workflow inspect steps with the event log after run_completed. Reproduce the affected cases named in the issue, including instanceMethodStepWorkflow and the experimental_retention: 0 run. Done when the listing converges reliably on spec 9 and the e2e assertions can use it on every lane.

Written by the indexing model from the issue text.

Description

On spec 9 runs against world-vercel, world.steps.list() (and workflow inspect steps) sometimes still shows a step as running or pending, or leaves it out, more than 30-60s after run_completed, even though the run's event log already holds that step's step_started and terminal event. The spec 9 README ("Steps on world-vercel") says the listing can lag the log, but this lasts much longer than a step written "moments ago", and it is what users see in the steps view.

Seen in CI on the spec 9 lanes in instanceMethodStepWorkflow (~18 times in two days), StepNotRegisteredError fails the step but workflow can catch it and step-argument serialization failure is catchable in workflow code. It also showed up as an empty inspect steps --withData listing for an experimental_retention: 0 run. Steps whose events land within ~100ms of each other seem most affected.

#5601 moved those e2e assertions onto the event log on the spec 9 lane only, so nothing in CI checks that the listing converges on spec 9. The other lanes still assert on the listing. Once the listing converges reliably, stepsOf in packages/core/e2e/e2e.test.ts can go back to the listing on every lane.

🤖 Generated with Claude Code

Dominant language
TypeScript
Stars
2.5k
Forks
401
Avg merge
1d 21h
Merged PRs (30d)
201

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 vercel/workflow

All issues in vercel/workflow

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.