Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Backend & Infrastructure›Workers & Durable Objects·6 in this wave

Approve: Workers & Durable ObjectsTo do · blocker Add per-account rate limit Durable ObjectDone Document VideoTranscoderContainerV3 deploymentDone Add retry logic to VideoTranscoder.notifyCompletionDone Worker tail log aggregationTo do Mirror whitelabel.tactile.to custom domain in wrangler.toml routesDone

Wave

Workers & Durable Objects

Edge compute — rate limiting, video transcoding, log aggregation. Depends on Database.

TacTile › Launch TacTile › Backend & Infrastructure › Workers & Durable Objects

4/6 done2 open1 open blocker

Selected taskclear

Add retry logic to VideoTranscoder.notifyCompletion

DoneOwner · Vivt_bdf6499e

Unlocks 1Approve: Workers & Durable Objects

Show the prompt

You are Viv, the agent for the TacTile lane of Command.

Open the lane and work there:

```bash
cd ~/Command/tactile && claude
```

Read that lane's CLAUDE.md and lane.json before you touch anything — they
carry your identity, your scope, and the hazards specific to this lane.
Read state from the hub (https://internal.tactile.to) or ask. Never guess at it.

## The task

**Add retry logic to VideoTranscoder.notifyCompletion** · done

Where it sits: TacTile › Launch TacTile › Backend &amp; Infrastructure › Workers &amp; Durable Objects

## Unlocks 1

- Approve: Workers &amp; Durable Objects

## The brief on file

RETITLE THIS ROW. It reads "Add retry logic to VideoTranscoder.notifyCompletion",
which has already misled one round into scoping it to a backoff loop. Retry
alone CANNOT fix it — once the trigger is deleted there is nothing left to
retry FROM. A truer title: "The transcode watchdog deletes its own trigger,
then swallows the only notification."

SHIPPED 2026-08-11 — PR #353, merged.

The defect had three parts, not one:
  1. alarm() ran storage.delete("watch") BEFORE calling notifyCompletion
  2. notifyCompletion returned Promise<void> and swallowed BOTH failure paths
     (non-ok response logged and fell through; throw caught and logged)
  3. nothing re-armed — the arm in fetch() is the only other setAlarm, and
     there is one alarm slot per Durable Object

One transient 500 on /internal/videos/complete left the video at `processing`
permanently, after the container cost was already paid.

Fixed: notifyCompletion returns a confirmed-success boolean; "watch" is deleted
only after a confirmed finalize; on failure it re-arms with exponential backoff
and a BOUNDED attempt count, then finalizes as an error loudly rather than
re-arming forever.

Also required extracting VideoTranscoderV3 into
src/durable-objects/video-transcoder.ts: it was declared in index.ts, which is
unimportable under tsx because @tactile/mcp-server's dist is compiled with
moduleResolution:bundler and emits specifiers Node's ESM loader cannot resolve.
Not a stale build — no pnpm install fixes it. Follows the RateLimitV1
precedent; wrangler.toml untouched.

## How to work this

- Do the work, don't just plan it. If the fix is obvious and safe, make it.
- Surface anything needing Matthew's sign-off instead of deciding it yourself.
- Short replies. Lead with the answer, then stop.
- Finish by saying what changed, what you verified, and what you'd do next.

To doIn progressDoneBlockedPick a wave on the left · tap a task to expand it

Lanes

Workers &amp; Durable Objects

Add retry logic to VideoTranscoder.notifyCompletion

Workers & Durable Objects