← All workshopsRead Resume Botie’s Work with LangGraph

Agents

Restore the request before merging the manual update

BOTIE

Connect checkpoint records and the selected thread ID to Load this thread’s evidence. Inspect the excerpts before adding any updates.
Ready to test
0 passed · 0 failed · 2 not run

An empty floor. Start with the information your machine needs.

Received result

Your answer will arrive here.

Examples, experiments and workspace controls
Live values

Connect a tool's inputs to see what it produces. You can try a branch before connecting it to Result.

Try your own inputs

Use a copy of the example to try your own data. Keep the problem's assumptions in mind, and predict the effect of a change before checking the output. You can also add another branch to compare two ways of doing the calculation.

Start at an output arrow, then click or drag to an input. Drag empty space to pan. Delete removes a selection. Ctrl/Cmd+Z undoes a change.
Context for this challenge

Connect checkpoint records and the selected thread ID to Load this thread’s evidence. Inspect the excerpts before adding any updates.

A technician resumes a maintenance request while a revised excerpt arrives. Keep that request’s evidence coherent.

Inspect the component calculation
Load this thread's evidence(
  Checkpoint records by thread: Evidence lists saved by thread ID
  Thread ID: Thread to resume
)
Examples and results
Evidence lists saved by thread ID
{
  "request-17": [
    {
      "id": "M7",
      "text": "Inspect mounting."
    }
  ]
}
Thread to resume
request-17
Required result
[
  {
    "id": "M7",
    "text": "Inspect mounting."
  }
]
Evidence lists saved by thread ID
{
  "request-17": [
    {
      "id": "M7",
      "text": "Mounting."
    }
  ],
  "request-28": [
    {
      "id": "M2",
      "text": "Filter."
    }
  ]
}
Thread to resume
request-28
Required result
[
  {
    "id": "M2",
    "text": "Filter."
  }
]
Try a fresh construction

This clears this draft, including its undo history. Earlier successful attempts stay recorded. Build again without opening hints to record an independent attempt.

Stuck? Inspect a worked construction

The tools below form one possible solution. You can assemble it, follow its signals, and undo that change to return to your own construction.

Assumptions and test precision

This is a sequential reducer demonstration. It does not persist real data, resolve concurrent conflicting versions, or execute an external job. Numerical tests allow a difference of 0.001. Lists and structures must also have the right shape.

Your last tested pieces can start the full construction. An existing draft there keeps its own pieces.

Replayed updates arrive in a different order

This check uses the pieces from “Resume the right request’s evidence”.

BOTIE

The saved request has M2 then M5. Incoming records update M5 first and M2 second. Predict the resulting evidence list while preserving the position where each ID first appeared.
Evidence lists saved by thread ID
{
  "R21": [
    {
      "id": "M2",
      "text": "Old coupling check."
    },
    {
      "id": "M5",
      "text": "Old alignment check."
    }
  ]
}
Thread to resume
R21
New or revised excerpt records
[
  {
    "id": "M5",
    "text": "Revised alignment check."
  },
  {
    "id": "M2",
    "text": "Revised coupling check."
  }
]

Use a number, text, or an array matching the requested result. For a matrix, put each row in brackets. Saving your prediction runs your current construction on these inputs and checks the earlier examples too.

Build a construction in the workspace above first. This case will test those pieces.

Does replay-safe evidence merging also guarantee that a work-order API cannot create duplicates?

A reducer governs state updates. External writes need their own idempotency policy at the service receiving the action.

This is a sequential reducer demonstration. It does not persist real data, resolve concurrent conflicting versions, or execute an external job.

Work through the Python challenges →
Continue the courseAsk Before Botie Creates the Inspection Job →
← Put Limits Around a LangChain Agent