All Docs
FeaturesDepositClearUpdated March 13, 2026

Blog: Keeping Your Threads Tidy — Automatic Negotiation Thread Closure

Keeping Your Threads Tidy — Automatic Negotiation Thread Closure

Release v0.1.284

One of the small frustrations in managing deposit releases is the loose end left behind after a case resolves: a negotiation thread that remains open even though the underlying deposit has already been released or escalated to dispute. From today, that loose end ties itself.

What We Shipped

We've introduced an event-driven workflow that listens for deposit release status changes. The moment a release transitions to either released or disputed, the platform automatically finds the linked negotiation thread and — if it's still open — closes it cleanly.

Here's exactly what happens:

  1. The deposit release reaches released or disputed status.
  2. The system looks up the associated negotiation thread.
  3. If the thread is still open, it is closed with a timestamp and a system note explaining why.
  4. Org admins receive a notification confirming the closure (or a warning if no open thread was found).
  5. Everything is written to the audit log.

Why It Matters

Negotiation threads exist to facilitate back-and-forth between parties during the deposit resolution process. Once the release is resolved — one way or another — that conversation has served its purpose. Leaving threads open indefinitely creates noise in admin dashboards, risks confusion if parties re-engage on a settled matter, and adds unnecessary clutter to the audit trail.

By automatically closing threads at the right moment, we ensure that the state of your negotiation threads always accurately reflects the state of the deposit.

What You'll See

  • As an org admin: You'll receive a success notification whenever a thread is auto-closed following a release resolution. If we expect a thread but don't find an open one, you'll get a warning — so nothing slips past unnoticed.
  • As a thread participant: The thread will show a system note explaining it was closed because the associated deposit was resolved or disputed, along with the exact timestamp.
  • In the audit log: Every auto-close is recorded, giving you a clear, queryable history of when and why each thread was closed.

No Action Required

This is fully automatic. There's nothing to configure and no workflow to enable — the trigger fires on every qualifying release status change, for every organisation, from today.

Released in v0.1.284. See the full changelog for details.