chatwoot-router 0.5.0 → 0.5.2

package/CHANGELOG.md

@@ -7,6 +7,21 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.5.2] - 2026-10-05
+
+## [0.5.1] - 2026-10-05
+
+### Fixed
+
+- Route on a customer's message as it arrives. Chatwoot's message webhook describes a contact without a `type`
+  (`Contact#webhook_data`; users and bots have one), and the router required `type: "contact"`, so it ignored
+  every customer message and a new ticket waited for the five-minute sweep.
+
+### Fixed
+
+- Clear a request's timeout once its response has been read. The pending `AbortSignal.timeout` timer kept a
+  Durable Object invocation open until it fired, so most alarms were billed and reported at about 60 seconds.
+
 ## [0.5.0] - 2026-10-05
 
 ### Fixed
@@ -112,7 +127,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   `routing_kind`.
 - The `chatwoot-router-store-config` command and `chatwoot-router/stored-config`, for a configuration in KV.
 
-[Unreleased]: https://github.com/Phala-Network/chatwoot-workers/compare/chatwoot-router@0.5.0...HEAD
+[Unreleased]: https://github.com/Phala-Network/chatwoot-workers/compare/chatwoot-router@0.5.2...HEAD
+[0.5.2]: https://github.com/Phala-Network/chatwoot-workers/compare/chatwoot-router@0.5.1...chatwoot-router@0.5.2
+[0.5.1]: https://github.com/Phala-Network/chatwoot-workers/compare/chatwoot-router@0.5.0...chatwoot-router@0.5.1
 [0.5.0]: https://github.com/Phala-Network/chatwoot-workers/compare/chatwoot-router@0.4.0...chatwoot-router@0.5.0
 [0.4.0]: https://github.com/Phala-Network/chatwoot-workers/compare/chatwoot-router@0.3.0...chatwoot-router@0.4.0
 [0.3.0]: https://github.com/Phala-Network/chatwoot-workers/compare/chatwoot-router@0.2.0...chatwoot-router@0.3.0

package/README.md

@@ -148,37 +148,6 @@ the Router DO during rollback. If its state is lost or restored to an older reco
 and isolate conversations with uncertain attempts/turns for owner review; a currently empty history does not
 prove another send is safe. Existing pending conversations are reconciled; non-pending conversations stay with people. The user token must see all relevant inboxes.
 
-For the first move from the relay's built-in routing (production baseline 0.27.0):
-
-1. Record the live relay deployment/version id and CONFIG_KEY before rollout; retain its Hub and old secrets.
-   Disconnect all brand bots and prevent competing old deployments. Verify bot identities, owner membership,
-   labels, canned responses and inbox visibility. Historical confirmed brand-bot replies need no ledger migration.
-2. Deploy and verify relay 0.30 first. Remove `routing`, `router.accounts` and `router.waitSeconds`; keep every kind
-   in `router.keepLabels`. Verify the actual version and that built-in routing/in-flight old work stopped.
-3. Bootstrap this Worker by hand with all four secrets in a protected secrets file while bots remain disconnected.
-   Verify KV/domain, upstream permissions and test tickets; health/2xx alone do not prove routing success.
-   If using an infra PR whose push deploys both Workers independently, merge only after both hand deployments pass.
-4. Connect bots one account at a time and verify real routing, handoff, failed/unknown reply handling, historical
-   reply deduplication and Discord/triage behavior, including at least a complete sweep.
-5. To roll back, disconnect bots first and **keep this router running until no pending ticket remains assigned to
-   a disconnected brand bot and no non-pending ticket remains assigned to that bot**. Complete pending/open
-   account passes and let failed ending releases finish through their durable retries: pending uses native bot
-   handoff, open leftovers use explicit unassignment, and kind endings release resolved/snoozed tickets in the
-   same turn. Confirm cleared bot ownership across statuses; preserve human/other-bot owners. Then stop
-   webhook entry, cron and queued/in-flight router work; stopping cron alone does not cancel DO alarms. Preserve DO
-   namespace and storage, including reply and turn guards. Restore the recorded live 0.27 version **and its
-   CONFIG_KEY**, without overlapping old/new routing. Relay 0.27 uses its original Hub's
-   `kind-reply:<account>:<conversation>` records; the Router uses separate `reply:<account>:<conversation>`
-   records. Restoring code/config does not copy Router attempts into the Hub or reset either ledger. Only replies
-   already recorded by 0.27 retain its own reply-once protection; Router-only replies/unknown attempts can be
-   attempted again by 0.27. Keep both DOs and review/isolate those tickets before restoring old routing. Rollback
-   does not guarantee reply-once across this switch or undo sent messages or other mutations.
-
-Current router upgrades need no custom coordination attributes, compatibility effects or one-time lifecycle
-cleanup. Older unreadable job payloads are dropped; live snapshots and the account sweep reconstruct queued work, not durable reply/turn guards.
-If handoff credentials fail, repair them or let a real owner take the tickets; do not bulk-open with the integration
-user token, which can assign every ticket to that user. Keep old attributes through the owner's rollback window.
-
 Redaction is best effort, not anonymization: other personal information can still reach TypeSafe. Logs contain
 ids and outcomes, never message bodies or credentials. See [SECURITY.md](https://github.com/Phala-Network/chatwoot-workers/blob/main/SECURITY.md),
 [CONTRIBUTING.md](https://github.com/Phala-Network/chatwoot-workers/blob/main/CONTRIBUTING.md) and [CHANGELOG.md](https://github.com/Phala-Network/chatwoot-workers/blob/main/packages/chatwoot-router/CHANGELOG.md). Licensed under [MIT](https://github.com/Phala-Network/chatwoot-workers/blob/main/packages/chatwoot-router/LICENSE).

package/lib/packages/chatwoot-router/src/index.js

@@ -95,10 +95,30 @@ var Budget = class {
     if (this.used >= this.limit) throw new BudgetExhaustedError();
     this.used += 1;
   }
-  fetch = (request) => {
-    if (this.used >= this.limit) return Promise.reject(new BudgetExhaustedError());
+  /**
+   * The timeout is cleared once the response body has been read (or there is none): a pending
+   * timer, such as `AbortSignal.timeout`'s, keeps the invocation open until it fires.
+   */
+  fetch = async (request) => {
+    if (this.used >= this.limit) throw new BudgetExhaustedError();
     this.used += 1;
-    return this.fetchImpl(new Request(request, { signal: AbortSignal.timeout(this.timeoutMs) }));
+    const controller = new AbortController();
+    const timer = setTimeout(
+      () => controller.abort(new DOMException("The request timed out", "TimeoutError")),
+      this.timeoutMs
+    );
+    try {
+      const response = await this.fetchImpl(new Request(request, { signal: controller.signal }));
+      if (!response.body) {
+        clearTimeout(timer);
+        return response;
+      }
+      const body = response.body.pipeThrough(new TransformStream({ flush: () => clearTimeout(timer) }));
+      return new Response(body, response);
+    } catch (error) {
+      clearTimeout(timer);
+      throw error;
+    }
   };
 };
 
@@ -1281,7 +1301,8 @@ function eventTarget(payload) {
       ...change && (change.previous_value === "pending" || change.current_value === "resolved" || change.current_value === "pending" && change.previous_value !== "resolved") && event.updated_at !== void 0 ? { transition: { status: change.current_value, at: event.updated_at } } : {}
     };
   }
-  if (event.event === "message_created" && (event.message_type === "incoming" || event.message_type === 0) && !event.private && event.sender?.type === "contact" && event.id !== void 0 && event.conversation) {
+  if (event.event === "message_created" && (event.message_type === "incoming" || event.message_type === 0) && !event.private && // A contact's webhook data has no `type` (Contact#webhook_data); a user's and a bot's do.
+  (event.sender?.type ?? "contact") === "contact" && event.id !== void 0 && event.conversation) {
     return { accountId: event.account.id, conversationId: event.conversation.id };
   }
   return void 0;

package/lib/shared/budget.d.ts

@@ -11,5 +11,9 @@ export declare class Budget {
     get remaining(): number;
     /** Counts a request that is not a fetch, such as a call to another Durable Object. */
     consume(): void;
+    /**
+     * The timeout is cleared once the response body has been read (or there is none): a pending
+     * timer, such as `AbortSignal.timeout`'s, keeps the invocation open until it fires.
+     */
     readonly fetch: Fetch;
 }

package/lib/shared/chatwoot/api.d.ts

@@ -232,8 +232,6 @@ export declare function personAssignee(conversation: ChatwootConversation): {
         custom_role?: Record<string, unknown> | null;
     }[];
 } | undefined;
-/** An actual public answer; Chatwoot templates include greetings and out-of-office notices. */
-export declare function isAnsweringReply(message: ChatwootMessage): boolean;
 export declare function toRelayConversation(conversationId: number, conversation: ChatwootConversation): RelayConversation;
 export declare function toRelayMessage(message: ChatwootMessage, context: {
     account: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chatwoot-router",
-  "version": "0.5.0",
+  "version": "0.5.2",
   "description": "Route Chatwoot conversations with TypeSafe Jev on Cloudflare Workers.",
   "keywords": [
     "chatwoot",