Skip to content
Flue Agent Workshop

Recovery lane

Recovery lane

Section titled “Recovery lane”

Getting stuck is normal. Staying stuck is optional. Choose the situation that matches what happened and use the smallest recovery action.

The room moved ahead

Section titled “The room moved ahead”

Replace cp/4-subagent with the branch displayed by the facilitator:

If Vite is running, first press Ctrl+C in its terminal. A running process can retain the previous checkpoint’s generated Worker, bindings, or container configuration.

Terminal window
git stash push --include-untracked -m "workshop recovery"
git fetch origin
git branch -f workshop-backup HEAD
git switch --no-track -C workshop origin/cp/4-subagent
npm ci

Then follow the checkpoint’s Live deploy tab: deploy the selected branch and run its verification commands before proceeding. For Local dev, restart npm run dev after the install. The stash keeps your work for later review.

I want to retry the current exercise

Section titled “I want to retry the current exercise”

Switch to the previous checkpoint branch. To retry checkpoint 4, restart from cp/3-api-tools:

If a dev server is running, press Ctrl+C in its terminal before switching.

Terminal window
git stash push --include-untracked -m "retry checkpoint 4"
git fetch origin
git branch -f workshop-backup HEAD
git switch --no-track -C workshop origin/cp/3-api-tools
npm ci

Rebuild the exercise, then deploy and verify it from its Live deploy tab. For Local dev, restart npm run dev after the clean install.

My conversation is confusing the test

Section titled “My conversation is confusing the test”

Use a fresh conversation ID. Durable Object history is keyed by that ID:

Terminal window
npm run deploy
sleep 5
npm run smoke -- https://field-trip-agent.<subdomain>.workers.dev cp4-retry-live-1 "Find venues for an offsite in Lisbon"

Save your workers.dev subdomain to open this test ↗https://field-trip-agent.<subdomain>.workers.dev/?id=cp4-retry-live-1

This opens the same conversation as the smoke test. If you repeat this checkpoint, before copying its commands.

If you truly need a clean local data store, stop Vite and remove its state:

Terminal window
rm -rf .wrangler/state

Prefer the guide’s use a fresh test ID control during the workshop because it is faster and does not erase every local conversation.

I want my stashed changes back

Section titled “I want my stashed changes back”

Inspect before applying:

Terminal window
git stash list
git stash show --stat stash@{0}
git stash apply stash@{0}

Apply the stash after the workshop or on a separate branch. It may conflict with the checkpoint you jumped to, which is why recovery does not automatically pop it.