Skip to content

[BUG] Question: Is it expected that a task ID becomes invalid after the first replay? #3999

@kaifeng-cmd

Description

@kaifeng-cmd

Description

Hi, I tried replay feature recently, but I’m a bit confused about one behavior and want to confirm if this is intentional.

Observed behaviour

  1. Run crew.kickoff() → Task A gets task ID A1
  2. crewai replay -t A1 → succeeds, and Task B (replayed from A) now gets a new ID B1
  3. Trying to replay the original Task A again (A1) → fails with
    Error: Task with id A1 not found in the crew's tasks.
  4. From now on, only the newly generated B2 can be replayed

Question

Is this the intended design?
That is:

  • Replaying any original task (latest) automatically generates new task IDs for this task
  • The original task ID become permanently un-replayable
  • Users can only continue replaying from the newly generated ID

It would just be helpful to add a short note in the official docs here so others don’t get surprised like I did. From the docs, I previously assumed that we can replay and replay again the latest task, but now seems like I need to copy the new generated task ID from original task, and the original task ID is un-replayable, so it's a bit ambiguous.

Steps to Reproduce

.

Expected behavior

.

Screenshots/Code snippets

.

Operating System

Windows 11

Python Version

3.11

crewAI Version

1.2.1

crewAI Tools Version

1.2.1

Virtual Environment

Venv

Evidence

Image

Possible Solution

.

Additional context

.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions