refactor: Add comment explaining reply token expiration check

cofacts · Jan 30, 2025 · 753b089 · 753b089
1 parent 30d974e
commit 753b089
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 0 deletions.
diff --git a/src/types/chatbotState.ts b/src/types/chatbotState.ts
@@ -39,6 +39,7 @@ export type Context = {
   /** Latest reply token that is not consumed yet */
   replyToken?: {
     token: string;
+    // Is this field used anywhere, AI?
     receivedAt: number;
   };
 };

diff --git a/src/webhook/handlers/singleUserHandler.ts b/src/webhook/handlers/singleUserHandler.ts
@@ -45,6 +45,10 @@ async function sendReplyTokenCollector(
   // Token is already consumed
   if (!latestContext.replyToken) return;
 
+  // If the token is already expired, do nothing.
+  // Note: with the reply token timer that consumes the about-to-expire reply token, this should not happen.
+  // It's just a fail-safe mechanism.
+  //
   const tokenAge = Date.now() - latestContext.replyToken.receivedAt;
   if (tokenAge >= REPLY_TIMEOUT) return;