improvement(processing): reduce redundant DB queries in execution preprocessing by waleedlatif1 · Pull Request #3320 · simstudioai/sim

waleedlatif1 · 2026-02-24T14:51:49Z

Summary

Thread subscription through usage-limit call chain to eliminate redundant getHighestPrioritySubscription fetches per execution
Reuse preprocessResult.workflowRecord in background execution instead of re-fetching with getWorkflowById
Pass workspaceId to loadDeployedWorkflowState to skip internal workflow table re-query
Pass pre-fetched workflow record from authorization into preprocessing to skip duplicate Step 1 query
Refactor execution-core completion handling for clarity

Test plan

bunx tsc --noEmit passes clean
bun run lint passes clean
Verify workflow execution via manual test or staging deploy
All parameter additions are optional with backward-compatible defaults — no breaking changes

…processing Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

vercel · 2026-02-24T14:51:55Z

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Feb 24, 2026 7:49pm

waleedlatif1 · 2026-02-24T14:52:40Z

@cursor review

waleedlatif1 · 2026-02-24T14:52:43Z

@greptile

greptile-apps · 2026-02-24T14:54:45Z

Greptile Summary

This PR reduces redundant database queries in the execution preprocessing pipeline by threading pre-fetched data (workflow records, subscription info, workspace IDs) through call chains instead of re-querying. It also removes verbose logger.debug statements across ~30 files, replaces several as any casts with proper types, removes dead code (getSnapshotByHash, setupExecutor), and refactors execution-core.ts to use a fire-and-forget pattern for post-execution logging/billing.

DB query reduction: Subscription is fetched once in preprocessing and threaded into checkServerSideUsageLimits → checkUsageStatus → getUserUsageLimit. Workflow record from authorization is passed to preprocessing to skip the Step 1 query. workspaceId is passed to loadDeployedWorkflowState to skip re-querying the workflow table.
Fire-and-forget refactor in execution-core.ts: Post-execution logging, billing updates, run-count updates, and cancellation cleanup are now wrapped in void (async () => {...})(). This speeds up response time but introduces risk of silent data loss if the process exits before the IIFE settles — relevant for Trigger.dev background jobs and serverless functions.
Race condition guard in LoggingSession: Added completing flag and completionPromise to prevent concurrent completion attempts. However, completeWithPause was not updated with this guard, creating an inconsistency.
Type safety improvements: Replaced as any casts with proper types in logger.ts, search-suggestions.ts, state/route.ts, deploy/route.ts, and status/route.ts.
Debug log cleanup: Removed ~100+ logger.debug calls across webhook processors, polling services, billing, knowledge search, and execution files.

Confidence Score: 3/5

The DB query optimizations and type safety improvements are solid, but the fire-and-forget pattern in execution-core.ts and missing race-condition guard in completeWithPause introduce risks that should be addressed before merging.
The bulk of this PR (subscription threading, workflowRecord reuse, debug log removal, type improvements) is clean and low-risk. However, two issues lower the confidence: (1) the fire-and-forget pattern in execution-core.ts could silently drop execution logs and billing updates in serverless/background-job contexts, and (2) completeWithPause is missing the completing guard that was added to every other completion method, creating a race condition for paused executions.
Pay close attention to apps/sim/lib/workflows/executor/execution-core.ts (fire-and-forget logging risk) and apps/sim/lib/logs/execution/logging-session.ts (inconsistent completing guard in completeWithPause).

Important Files Changed

Filename	Overview
apps/sim/lib/workflows/executor/execution-core.ts	Post-execution logging/billing/cleanup moved to fire-and-forget `void (async () => {...})()` pattern. Risk of silent data loss if the process exits before the IIFE completes, especially in serverless/Trigger.dev contexts.
apps/sim/lib/logs/execution/logging-session.ts	Added `completing` flag and `completionPromise` for race-condition prevention. `completeWithPause` is missing both the `completing` guard and `this.completing = false` on error, creating an inconsistency across completion methods.
apps/sim/lib/execution/preprocessing.ts	Accepts optional pre-fetched workflow record and threads subscription through usage/rate-limit checks. Reorders steps 5/6. Logic is sound — the subscription function has its own error handling so the removed try/catch is safe.
apps/sim/lib/billing/calculations/usage-monitor.ts	Added optional `preloadedSubscription` parameter to avoid redundant DB queries. Backward-compatible, no logic changes.
apps/sim/lib/billing/core/usage.ts	Added optional `preloadedSubscription` parameter to `getUserUsageLimit`. Correctly uses `!== undefined` to distinguish "not provided" from "null subscription". Clean change.
apps/sim/lib/billing/core/plan.ts	Exports `HighestPrioritySubscription` type alias for use across the codebase. Minimal, clean change.
apps/sim/lib/workflows/persistence/utils.ts	Accepts optional `providedWorkspaceId` to skip re-querying workflow table. Backward-compatible with correct fallback logic.
apps/sim/app/api/workflows/[id]/execute/route.ts	Threads workflow record from authorization into preprocessing. Removes duplicate error-logging calls (now handled by execution-core). Cleanup cache changed to fire-and-forget. Sound refactoring.
apps/sim/background/workflow-execution.ts	Reuses `preprocessResult.workflowRecord` instead of re-fetching. The outer catch block calls `safeCompleteWithError` which may race with the fire-and-forget logging in execution-core, though the new `completionPromise` guard should deduplicate.
apps/sim/background/schedule-execution.ts	Removed debug-level success logs from `applyScheduleUpdate`. Passes `workspaceId` to `loadDeployedWorkflowState`. Clean simplification.

Sequence Diagram

sequenceDiagram
participant Client
participant ExecuteRoute as execute/route.ts
participant AuthZ as authorizeWorkflow
participant Preprocess as preprocessExecution
participant SubDB as Subscription DB
participant UsageCheck as checkServerSideUsageLimits
participant Core as executeWorkflowCore
participant Logging as LoggingSession
Client->>ExecuteRoute: POST /workflows/{id}/execute
ExecuteRoute->>AuthZ: authorizeWorkflowByWorkspacePermission()
AuthZ-->>ExecuteRoute: {workflow record}
ExecuteRoute->>Preprocess: preprocessExecution({workflowRecord})
Note over Preprocess: Skip Step 1 DB query (reuse record)
Preprocess->>SubDB: getHighestPrioritySubscription(actorUserId)
SubDB-->>Preprocess: subscription (fetched once)
Preprocess->>UsageCheck: checkServerSideUsageLimits(userId, subscription)
Note over UsageCheck: Reuses subscription (no re-fetch)
UsageCheck-->>Preprocess: {isExceeded, ...}
Preprocess-->>ExecuteRoute: {workflowRecord, subscription, ...}
ExecuteRoute->>Core: executeWorkflowCore(snapshot, ...)
Core->>Core: Execute workflow blocks
Core-->>ExecuteRoute: result (returned immediately)
Note over Core,Logging: Fire-and-forget (void async)
Core->>Logging: safeComplete / safeCompleteWithError
Logging->>Logging: DB update (may race with process exit)

_{Last reviewed commit: 2860663}

greptile-apps

_{10 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

waleedlatif1 · 2026-02-24T14:59:25Z

@cursor review

…ow record Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

waleedlatif1 · 2026-02-24T17:39:45Z

@cursor review

waleedlatif1 · 2026-02-24T17:39:50Z

@greptile

greptile-apps

_{10 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

Replace `as any` cast in non-SSE error path with proper `buildTraceSpans()` transformation, matching the SSE error path. Remove redundant `as any` cast in preprocessing.ts where the types already align. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

waleedlatif1 · 2026-02-24T17:50:49Z

@greptile

waleedlatif1 · 2026-02-24T17:50:54Z

@cursor review

greptile-apps

_{10 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

…logging - logger.ts: cast JSONB cost column to `WorkflowExecutionLog['cost']` instead of `any` in both `completeWorkflowExecution` and `getWorkflowExecution` - logger.ts: replace `(orgUsageBefore as any)?.toString?.()` with `String()` since COALESCE guarantees a non-null SQL aggregate value - logging-session.ts: cast JSONB cost to `AccumulatedCost` (the local interface) instead of `any` in `loadExistingCost` Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

…e in usage.ts Replace inline `Awaited<ReturnType<typeof getHighestPrioritySubscription>>` with the already-exported `HighestPrioritySubscription` type alias. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

waleedlatif1 · 2026-02-24T17:57:30Z

@cursor review

… types - preprocessing.ts: use exported `HighestPrioritySubscription` type instead of redeclaring via `Awaited<ReturnType<...>>` - deploy/route.ts, status/route.ts: cast `hasWorkflowChanged` args to `WorkflowState` instead of `any` (JSONB + object literal narrowing) - state/route.ts: type block sanitization and save with `BlockState` and `WorkflowState` instead of `any` - search-suggestions.ts: remove 8 unnecessary `as any` casts on `'date'` literal that already satisfies the `Suggestion['category']` union Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

…tion When executeWorkflowCore throws, its catch block fire-and-forgets safeCompleteWithError, then re-throws. The caller's catch block also fire-and-forgets safeCompleteWithError on the same LoggingSession. Both check this.completed (still false) before either's async DB write resolves, so both proceed to completeWorkflowExecution which uses additive SQL for billing — doubling the charged cost on every failed execution. Fix: add a synchronous `completing` flag set immediately before the async work begins. This blocks concurrent callers at the guard check. On failure, the flag is reset so the safe* fallback path (completeWithCostOnlyLog) can still attempt recovery. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

…vent completion races Move waitForCompletion() into markAsFailed() so every call site is automatically safe against in-flight fire-and-forget completions. Remove the now-redundant external waitForCompletion() calls in route.ts. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

waleedlatif1 · 2026-02-24T19:12:54Z

@cursor review

waleedlatif1 · 2026-02-24T19:12:58Z

@greptile

…empty catch - completeWithCostOnlyLog now resets this.completing = false when the fallback itself fails, preventing a permanently stuck session - Use _disconnectError in MCP test-connection to signal intentional ignore Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Revert unrelated debug log removal — this file isn't part of the processing improvements and the log aids connection leak detection. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

greptile-apps

_{51 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

waleedlatif1 · 2026-02-24T19:22:08Z

@cursor review

- preprocessing.ts: use undefined (not null) for failed subscription fetch so getUserUsageLimit does a fresh lookup instead of silently falling back to free-tier limits - deployed/route.ts: log warning on loadDeployedWorkflowState failure instead of silently swallowing the error - schedule-execution.ts: remove dead successLog parameter and all call-site arguments left over from logger.debug cleanup - mcp/middleware.ts: drop unused error binding in empty catch - audit/log.ts, wand.ts: promote logger.debug to logger.warn in catch blocks where these are the only failure signal Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

getHighestPrioritySubscription never throws (it catches internally and returns null), so the catch block in preprocessExecution is dead code. The null vs undefined distinction doesn't matter and the coercions added unnecessary complexity. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

…itySubscription getHighestPrioritySubscription catches internally and returns null on error, so the wrapping try/catch was unreachable dead code. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

No longer called after createSnapshotWithDeduplication was refactored to use a single upsert instead of select-then-insert. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

waleedlatif1 · 2026-02-24T19:49:59Z

@cursor review

waleedlatif1 · 2026-02-24T19:50:03Z

@greptile

cursor

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

greptile-apps

_{54 files reviewed, 3 comments}

_{Edit Code Review Agent Settings | Greptile}

greptile-apps · 2026-02-24T19:55:32Z

+ // Fire-and-forget: post-execution logging, billing, and cleanup
+ void (async () => {
+ try {
+ const { traceSpans, totalDuration } = buildTraceSpans(result)
+
+ if (result.success && result.status !== 'paused') {
+ try {
+ await updateWorkflowRunCounts(workflowId)
+ } catch (runCountError) {
+ logger.error(`[${requestId}] Failed to update run counts`, { error: runCountError })
+ }
+ }

- await loggingSession.safeComplete({
- endedAt: new Date().toISOString(),
- totalDurationMs: totalDuration || 0,
- finalOutput: result.output || {},
- traceSpans: traceSpans || [],
- workflowInput: processedInput,
- executionState: result.executionState,
- })
+ if (result.status === 'cancelled') {
+ await loggingSession.safeCompleteWithCancellation({
+ endedAt: new Date().toISOString(),
+ totalDurationMs: totalDuration || 0,
+ traceSpans: traceSpans || [],
+ })
+ } else if (result.status === 'paused') {
+ await loggingSession.safeCompleteWithPause({
+ endedAt: new Date().toISOString(),
+ totalDurationMs: totalDuration || 0,
+ traceSpans: traceSpans || [],
+ workflowInput: processedInput,
+ })
+ } else {
+ await loggingSession.safeComplete({
+ endedAt: new Date().toISOString(),
+ totalDurationMs: totalDuration || 0,
+ finalOutput: result.output || {},
+ traceSpans: traceSpans || [],
+ workflowInput: processedInput,
+ executionState: result.executionState,
+ })
+ }

- await clearExecutionCancellation(executionId)
+ await clearExecutionCancellation(executionId)
+ } catch (postExecError) {
+ logger.error(`[${requestId}] Post-execution logging failed`, { error: postExecError })
+ }
+ })()


Fire-and-forget may silently lose execution logs and billing
Wrapping all post-execution work (logging, billing, run-count updates, cancellation cleanup) in void (async () => {...})() means the function returns result before any of this completes. If the Node.js process shuts down or the serverless function's lifetime ends before the IIFE settles (common in edge/serverless environments, and also during Trigger.dev task completion), all of this work is silently dropped — no logs, no billing updates, no clearExecutionCancellation.
This is particularly risky because:
workflow-execution.ts (Trigger.dev background job) calls executeWorkflowCore, and after it returns, the Trigger.dev task may complete and the process may exit, racing against the fire-and-forget IIFE.
The same applies in the catch block (line ~417–440) where error logging is also fire-and-forget.
Consider either awaiting the post-execution work, or at minimum returning the completion promise so callers who can wait (like background jobs) have the option to await it.

greptile-apps · 2026-02-24T19:55:37Z

Additional Comments (2)

apps/sim/lib/logs/execution/logging-session.ts
Missing completing guard in completeWithPause

Every other completion method (complete, completeWithError, completeWithCancellation, completeWithCostOnlyLog) was updated with the new this.completing race-condition guard, but completeWithPause was not. Under the new fire-and-forget execution model in execution-core.ts, this method can now be called concurrently, and without the guard it could perform duplicate DB writes or fail to set this.completed = true.

 async completeWithPause(params: SessionPausedParams = {}): Promise<void> {
if (this.completed || this.completing) {
return
}
this.completing = true
try {

apps/sim/lib/logs/execution/logging-session.ts
Missing this.completing = false on error in completeWithPause

The catch block here does not reset this.completing = false, unlike the other completion methods (complete at line 326, completeWithError at line 439, completeWithCancellation at line 529, completeWithCostOnlyLog at line 879). If completeWithPause fails and completing isn't reset, subsequent retry attempts through safeCompleteWithPause will be blocked by the guard forever.

 } catch (pauseError) {
this.completing = false
logger.error(`Failed to complete paused logging for execution ${this.executionId}:`, {

…processing (simstudioai#3320) * improvement(processing): reduce redundant DB queries in execution preprocessing * improvement(processing): add defensive ID check for prefetched workflow record * improvement(processing): fix type safety in execution error logging Replace `as any` cast in non-SSE error path with proper `buildTraceSpans()` transformation, matching the SSE error path. Remove redundant `as any` cast in preprocessing.ts where the types already align. * improvement(processing): replace `as any` casts with proper types in logging - logger.ts: cast JSONB cost column to `WorkflowExecutionLog['cost']` instead of `any` in both `completeWorkflowExecution` and `getWorkflowExecution` - logger.ts: replace `(orgUsageBefore as any)?.toString?.()` with `String()` since COALESCE guarantees a non-null SQL aggregate value - logging-session.ts: cast JSONB cost to `AccumulatedCost` (the local interface) instead of `any` in `loadExistingCost` * improvement(processing): use exported HighestPrioritySubscription type in usage.ts Replace inline `Awaited<ReturnType<typeof getHighestPrioritySubscription>>` with the already-exported `HighestPrioritySubscription` type alias. * improvement(processing): replace remaining `as any` casts with proper types - preprocessing.ts: use exported `HighestPrioritySubscription` type instead of redeclaring via `Awaited<ReturnType<...>>` - deploy/route.ts, status/route.ts: cast `hasWorkflowChanged` args to `WorkflowState` instead of `any` (JSONB + object literal narrowing) - state/route.ts: type block sanitization and save with `BlockState` and `WorkflowState` instead of `any` - search-suggestions.ts: remove 8 unnecessary `as any` casts on `'date'` literal that already satisfies the `Suggestion['category']` union * fix(processing): prevent double-billing race in LoggingSession completion When executeWorkflowCore throws, its catch block fire-and-forgets safeCompleteWithError, then re-throws. The caller's catch block also fire-and-forgets safeCompleteWithError on the same LoggingSession. Both check this.completed (still false) before either's async DB write resolves, so both proceed to completeWorkflowExecution which uses additive SQL for billing — doubling the charged cost on every failed execution. Fix: add a synchronous `completing` flag set immediately before the async work begins. This blocks concurrent callers at the guard check. On failure, the flag is reset so the safe* fallback path (completeWithCostOnlyLog) can still attempt recovery. * fix(processing): unblock error responses and isolate run-count failures Remove unnecessary `await waitForCompletion()` from non-SSE and SSE error paths where no `markAsFailed()` follows — these were blocking error responses on log persistence for no reason. Wrap `updateWorkflowRunCounts` in its own try/catch so a run-count DB failure cannot prevent session completion, billing, and trace span persistence. * improvement(processing): remove dead setupExecutor method The method body was just a debug log with an `any` parameter — logging now works entirely through trace spans with no executor integration. * remove logger.debug * fix(processing): guard completionPromise as write-once (singleton promise) Prevent concurrent safeComplete* calls from overwriting completionPromise with a no-op. The guard now lives at the assignment site — if a completion is already in-flight, return its promise instead of starting a new one. This ensures waitForCompletion() always awaits the real work. * improvement(processing): remove empty else/catch blocks left by debug log cleanup * fix(processing): enforce waitForCompletion inside markAsFailed to prevent completion races Move waitForCompletion() into markAsFailed() so every call site is automatically safe against in-flight fire-and-forget completions. Remove the now-redundant external waitForCompletion() calls in route.ts. * fix(processing): reset completing flag on fallback failure, clean up empty catch - completeWithCostOnlyLog now resets this.completing = false when the fallback itself fails, preventing a permanently stuck session - Use _disconnectError in MCP test-connection to signal intentional ignore * fix(processing): restore disconnect error logging in MCP test-connection Revert unrelated debug log removal — this file isn't part of the processing improvements and the log aids connection leak detection. * fix(processing): address audit findings across branch - preprocessing.ts: use undefined (not null) for failed subscription fetch so getUserUsageLimit does a fresh lookup instead of silently falling back to free-tier limits - deployed/route.ts: log warning on loadDeployedWorkflowState failure instead of silently swallowing the error - schedule-execution.ts: remove dead successLog parameter and all call-site arguments left over from logger.debug cleanup - mcp/middleware.ts: drop unused error binding in empty catch - audit/log.ts, wand.ts: promote logger.debug to logger.warn in catch blocks where these are the only failure signal * revert: undo unnecessary subscription null→undefined change getHighestPrioritySubscription never throws (it catches internally and returns null), so the catch block in preprocessExecution is dead code. The null vs undefined distinction doesn't matter and the coercions added unnecessary complexity. * improvement(processing): remove dead try/catch around getHighestPrioritySubscription getHighestPrioritySubscription catches internally and returns null on error, so the wrapping try/catch was unreachable dead code. * improvement(processing): remove dead getSnapshotByHash method No longer called after createSnapshotWithDeduplication was refactored to use a single upsert instead of select-then-insert. ---------

improvement(processing): reduce redundant DB queries in execution pre…
79eaf18
…processing Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

waleedlatif1 changed the base branch from main to stagingFebruary 24, 2026 14:52

cursorBot reviewed Feb 24, 2026
View reviewed changes

Comment threadapps/sim/lib/workflows/executor/execution-core.ts
Comment threadapps/sim/app/api/workflows/[id]/execute/route.ts Outdated

greptile-appsBot reviewed Feb 24, 2026
View reviewed changes

cursorBot reviewed Feb 24, 2026
View reviewed changes

Comment threadapps/sim/app/api/workflows/[id]/execute/route.ts
Comment threadapps/sim/lib/execution/preprocessing.ts

improvement(processing): add defensive ID check for prefetched workfl…
9b201d8
…ow record Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

vercelBottemporarily deployed to Preview February 24, 2026 17:38 Inactive

cursorBot reviewed Feb 24, 2026
View reviewed changes

Comment threadapps/sim/lib/execution/preprocessing.ts
Comment threadapps/sim/app/api/workflows/[id]/execute/route.ts Outdated

greptile-appsBot reviewed Feb 24, 2026
View reviewed changes

vercelBottemporarily deployed to Preview February 24, 2026 17:50 Inactive

greptile-appsBot reviewed Feb 24, 2026
View reviewed changes

Comment threadapps/sim/lib/billing/core/usage.ts Outdated

vercelBottemporarily deployed to Preview February 24, 2026 17:55 Inactive

vercelBottemporarily deployed to Preview February 24, 2026 17:57 Inactive

vercelBottemporarily deployed to Preview February 24, 2026 18:03 Inactive

cursorBot reviewed Feb 24, 2026
View reviewed changes

Comment threadapps/sim/lib/workflows/executor/execution-core.ts

cursorBot reviewed Feb 24, 2026
View reviewed changes

Comment threadapps/sim/app/api/workflows/[id]/execute/route.ts
Comment threadapps/sim/lib/execution/preprocessing.ts

vercelBottemporarily deployed to Preview February 24, 2026 19:12 Inactive

cursorBot reviewed Feb 24, 2026
View reviewed changes

Comment threadapps/sim/lib/logs/execution/logging-session.ts
Comment threadapps/sim/app/api/mcp/servers/test-connection/route.ts

vercelBottemporarily deployed to Preview February 24, 2026 19:20 Inactive

fix(processing): restore disconnect error logging in MCP test-connection
6004fea
Revert unrelated debug log removal — this file isn't part of the processing improvements and the log aids connection leak detection. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

vercelBottemporarily deployed to Preview February 24, 2026 19:20 Inactive

greptile-appsBot reviewed Feb 24, 2026
View reviewed changes

cursorBot reviewed Feb 24, 2026
View reviewed changes

Comment threadapps/sim/lib/billing/core/usage.ts

vercelBottemporarily deployed to Preview February 24, 2026 19:37 Inactive

vercelBottemporarily deployed to Preview February 24, 2026 19:39 Inactive

improvement(processing): remove dead try/catch around getHighestPrior…
e1981b6
…itySubscription getHighestPrioritySubscription catches internally and returns null on error, so the wrapping try/catch was unreachable dead code. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

vercelBottemporarily deployed to Preview February 24, 2026 19:41 Inactive

improvement(processing): remove dead getSnapshotByHash method
2860663
No longer called after createSnapshotWithDeduplication was refactored to use a single upsert instead of select-then-insert. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

vercelBottemporarily deployed to Preview February 24, 2026 19:49 Inactive

cursorBot reviewed Feb 24, 2026
View reviewed changes

Comment threadapps/sim/lib/execution/preprocessing.ts
Comment threadapps/sim/lib/logs/execution/logging-session.ts

greptile-appsBot reviewed Feb 24, 2026
View reviewed changes

waleedlatif1 merged commit 9a31c7d into stagingFeb 24, 2026
12 checks passed

waleedlatif1 deleted the improvement/processing branch February 24, 2026 19:56

waleedlatif1 mentioned this pull request Feb 24, 2026
v0.5.100: multiple credentials, 40% speedup, gong, attio, audit log improvements #3326
Merged

Uh oh!

Conversation

waleedlatif1 commented Feb 24, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Test plan

Uh oh!

vercelBot commented Feb 24, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

waleedlatif1 commented Feb 24, 2026

Uh oh!

waleedlatif1 commented Feb 24, 2026

Uh oh!

Uh oh!

Uh oh!

greptile-appsBot commented Feb 24, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Summary

Confidence Score: 3/5

Important Files Changed

Sequence Diagram

Uh oh!

greptile-appsBot left a comment

Choose a reason for hiding this comment

Uh oh!

waleedlatif1 commented Feb 24, 2026

Uh oh!

Uh oh!

Uh oh!

waleedlatif1 commented Feb 24, 2026

Uh oh!

waleedlatif1 commented Feb 24, 2026

Uh oh!

Uh oh!

Uh oh!

greptile-appsBot left a comment

Choose a reason for hiding this comment

Uh oh!

waleedlatif1 commented Feb 24, 2026

Uh oh!

waleedlatif1 commented Feb 24, 2026

Uh oh!

greptile-appsBot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

waleedlatif1 commented Feb 24, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

waleedlatif1 commented Feb 24, 2026

Uh oh!

waleedlatif1 commented Feb 24, 2026

Uh oh!

Uh oh!

Uh oh!

greptile-appsBot left a comment

Choose a reason for hiding this comment

Uh oh!

waleedlatif1 commented Feb 24, 2026

Uh oh!

Uh oh!

waleedlatif1 commented Feb 24, 2026

Uh oh!

waleedlatif1 commented Feb 24, 2026

Uh oh!

cursorBot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

greptile-appsBot left a comment

Choose a reason for hiding this comment

Uh oh!

greptile-appsBotFeb 24, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-appsBot commented Feb 24, 2026

waleedlatif1 commented Feb 24, 2026•
edited
Loading

vercelBot commented Feb 24, 2026•
edited
Loading

greptile-appsBot commented Feb 24, 2026•
edited
Loading