Skip to Content

Features

Duplicates

How Docklee handles a capture that repeats one it already has.

Retries, double clicks, and replayed webhooks all send the same memory twice. Docklee catches repeats at three levels, so a retry never stores the same memory twice.

LevelCatchesWhat happens
In DockThe same content captured again within 60 secondsThe second capture is dropped before it's sent.
At the APIThe same content arriving again within 60 secondsThe event is rejected with duplicate_event.
In the memory spaceA new memory that states a fact the space already holdsThe existing memory is strengthened, and no new memory is stored.

Control what counts as the same

By default, two captures are the same when their text is the same. Pass a dedup key when your system already has an ID for the event, such as a message or webhook ID:

dock.capture(
    "Order 1042 was delivered.",
    type="event",
    dedup_key="order-1042-delivered",
)

A dedup key can be up to 256 characters. Two captures with the same key within 60 seconds count as one, even when their text differs.

A dedup key replaces the text check. Two different events that share a key within 60 seconds are treated as one, and the second is dropped.

Repeating on purpose

The 60-second window only stops accidental repeats. To record the same thing happening again, such as a second login, capture it after the window or give each occurrence its own dedup key.

Next steps

Repeats are handled. Learn when Dock sends your captures next.

On this page