perf(db): cut hot-path database work and close copilot cleanup gaps by waleedlatif1 · Pull Request #9419 · simstudioai/sim

waleedlatif1 · 2026-10-28T20:55:46Z

Summary

Cuts Sim's heaviest database work and closes cleanup gaps. Each change was checked against production query statistics and plans first; reads return the same results as before.

Billing

New usage_log_billing_entity_period_cost_idx (migration 0441) leads with both period stamps and carries the summed columns, so the billing-period sums and weekly refresh become index-only; it replaces two indexes (the old covering index lost to the slim one on column order and a misestimate)
Member removal revoked sessions (an organization row write) before locking the org's workspaces, the reverse of the storage writers' workspace-then-organization order, which deadlocked; revocation now runs after the handoff holds the workspace rows

Hot reads

The deployed-state read withholds the state blob when this process already caches that version (one round trip either way)
Audit-log lists read each scope branch through its keyset index and merge, instead of an OR the planner could only seq-scan; the cursor is a row comparison
Table-row mutations fetch only their workspace's table triggers instead of every workspace's

Files and knowledge

Workspace list invalidation broadcasts coalesce per tab while a refetch is in flight, so an upload burst no longer refetches the full list once per upload per viewer
The file-search backfill locks only the files it seeds, not every row it walks (its owner trigger was locking each one)
Completed-listing reconciliation counts window by window under the lease, so a large connector's count can't hit the statement timeout

Cleanup

Hard-deleting a copilot chat records its copilot backend and stored-file purge in the same transaction as the delete (outbox event, retried until it succeeds)
Account removal records the same purge for the chats it cascades away inside its transaction; admin user removal queues it, delayed, before the delete and refuses the removal if it can't
Outbox retention prunes completed checkpoint-expiry, file, memory and chat cleanup events; events read back by id are kept
Idempotency cleanup drops four full-table stat scans and resumes each batch where the last ended instead of rewalking from the oldest key

Schema (migration 0440)

Drops 32 indexes that a valid, unpredicated b-tree leads with the same columns (never unique or constraint-backing); checked against index usage on the primary and both replicas
Vacuums embedding, workspace_files and copilot_async_tool_calls at 2% dead/inserted instead of 20%

Type of Change

Bug fix
Other: performance

Testing

Unit: 20 apps/sim files (333 tests) plus packages/audit rollup tests
Integration: 43 files (661 pass, 2 skipped) against a freshly migrated database (0440 and 0441 applied) and a private Redis, including new suites for the lock order, deployed-state reads, audit-log scope paging, table triggers, chat backend cleanup, outbox retention, idempotency cleanup, file-search backfill and windowed counts; each new regression test fails on the pre-fix code
0441 replay verified: a valid index is kept, an invalid one is moved aside and rebuilt, an unexpected valid recovery index refuses
bun run check:migrations origin/staging, drizzle-kit generate (no changes), schema mock, Phase A generators (no changes), bun run lint, block registry, bun run check:audits (61), bun run type-check
The full bun run test runs in CI

Checklist

Code follows project style guidelines
Self-reviewed my changes
Tests added/updated and passing (new tests pass the test-audit authoring gate)
No new warnings introduced
I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

…handoff locks Member removal bumped the organization's security policy version, which row-locks the organization, and only then locked every organization workspace row for the shared-resource handoff. Storage writers lock a workspace row first and then its organization payer row, so a removal racing an upload or delete in one of the organization's workspaces deadlocked. Session revocation now runs after the handoff holds the workspace rows, keeping workspace rows before the organization row.

…e gate cache Both are single model calls gated on the payer's period usage, and both summed the ledger on every request. They now use the execution gate policy: a refusal is always re-read, and an admission is reused for at most the near-limit TTL when headroom is thin. A new chat turn's dispatch and the copilot validate callback keep reading the gate fresh.

…lready caches it loadDeployedWorkflowState selected the full state json on every call and only then consulted the in-process cache keyed by the immutable deployment version id, so a cache hit still shipped the whole snapshot from Postgres. The read now remembers which version each workflow last cached and asks Postgres to return NULL in place of state for that id, so a hit and a miss both stay one round trip and only a miss carries the blob. A hint left behind by an evicted entry falls through to the existing by-id read. The unused created_at projection is dropped too. An integration test pins the cold, warm, cutover, evicted-hint and undeployed paths against real Postgres.

The organization audit listing filtered on one predicate, workspace_id IN (org workspaces) OR (workspace_id IS NULL AND names the org), ordered by the millisecond-truncated timestamp. No index can return that OR in order, so Postgres collected and sorted every row in scope to return one page; for a busy organization the plan is a parallel sequential scan of audit_log, which on the replica runs long enough to be cancelled by recovery conflicts. The scope is a disjoint union, so the page's ids now come from one backward scan of audit_log_workspace_created_at_id_idx per workspace (a lateral join over the workspace ids) plus the organization-level rows, each stopping after limit + 1 matches; the first limit + 1 of their union are exactly the first limit + 1 of the whole scope, and the rows are then read by primary key in the same order. The keyset cursor becomes the equivalent row comparison, which the index scan seeks to directly instead of walking every newer row. queryAuditLogs takes the scope structurally; buildOrgScopeCondition is unchanged for the single-record read and the data drain. An integration test pages through mixed workspace, organization-level, foreign and departed-actor rows with sub-millisecond ties at several page sizes, with and without the byte budget, and asserts the exact sequence the single-predicate query returns.

fireTableTrigger runs after every committed table row mutation and loaded every active table-trigger webhook in the deployment, joined with its full workflow row, only to discard all but the mutated workspace's in JavaScript. It is the most frequent webhook query in production and its largest egress source. fetchActiveWebhooks takes an optional workspace scope that becomes a workflow.workspace_id predicate, and the table trigger passes its workspace, so a mutation in a workspace without table triggers reads nothing. The in-memory workspace check stays as a second guard. An integration test pins the scoped result to the unscoped result restricted to the workspace.

A workflow run's repeated table row changes and credential accesses merge into one audit row only while they fall inside the rollup window, two seconds after the first. Repeats spaced further apart, which is most scheduled runs that loop over slow tool calls, each opened a new row, so a run wrote several rows per table and credential where the audit log docs describe one. Inside a run's rollup scope, whose end writes every pending row anyway, the window is now a minute: a run's repeats share a row however far apart they fall, and a run whose process dies loses at most a minute of merged entries, within the best-effort durability the docs state. Rollups recorded outside a run keep the two-second window, and the per-row entry cap is unchanged, so no identifier or count is dropped.

The backfill walk locked every file of its page FOR SHARE, and its idempotent insert fired the revision owner trigger, which locks the file again, for every file that already had a revision. Each pass wrote a row lock into every live file's heap tuple. Walk without locks, check for an existing revision per row, and lock and reread only the files still missing one before inserting. The lock still keeps a content change from committing between the read and the insert, and a file deleted since the walk is now skipped instead of failing the page. Every owner the page passes is still woken.

A completed listing counted the connector's owned, listed, absent and tombstoned documents in one statement over every owned document. On the largest connectors that single read outlasts the statement timeout, so the reconciliation pass failed before it could walk anything. Sum the counts over the same bounded id windows the reconciliation walks scan, one statement per window, with the lease heartbeat between windows and the run deadline ending an unfinished count the way it ends an unfinished walk.

Every file mutation broadcasts a list-changed event to each open browser in the workspace, and each one invalidated the whole workspace file list at once. An API client uploading files one by one made every viewer refetch the full list once per upload, and invalidating a query mid-fetch cancels and restarts it, so a large workspace's list could be read many times over without one response landing. Deliver a room's changes one at a time: the first change is delivered at once, and changes that arrive while a delivery's refetch is in flight, or within a second after it settles, fold into one delivery after that.

…is hard-deleted DELETE /api/copilot/chat/delete removed the copilot_chats row but never told the copilot backend, so the backend's chat, events and runs for that chat were orphaned for good, and the chat's copilot/inline-image storage objects were never deleted. deleteCopilotChat now collects the chat's file refs with prepareChatCleanup before the delete transaction (the message rows that name them cascade away with it) and runs execute() after commit, which re-checks the row is gone, calls the backend's /api/tasks/cleanup and deletes the files. A failed purge is logged and does not turn the committed delete into an error response. Autopsy: the only callers of the backend cleanup were the retention jobs and the organization cleanup, and no test covered deleteCopilotChat's side effects outside Sim's rows: the integration suite only asserted that it stopped live runs. The new deletion.test.ts asserts the purge is prepared for the chat and executed after the delete, and fails on the previous code. Adds a central @sim/testing mock for @/lib/cleanup/chat-cleanup (its fourth test user) and moves the three existing local factories onto it.

…val cascades away copilot_chats cascades from user, workspace and workflow (and workflow from user and workspace), so deleting an account through POST /api/users/me/deletion, or a user row through /admin/remove-user, erased chat rows without ever telling the copilot backend, which kept those chats' data forever. A new outbox event, copilot.chat.backend-cleanup, carries up to 100 chat ids. Its handler purges only chats whose rows are gone and throws on a failed backend call, so the outbox retries it. Account deletion collects the chats its workspace and user deletes cascade (the account's own chats, chats in the doomed workspaces, and chats on workflows the account created or those workspaces hold) and queues the events in its transaction, so a rollback queues nothing. /admin/remove-user deletes outside any transaction, so its Better Auth delete hooks read the chat ids before the delete and queue the events after it commits, as they already do for run stops. Nothing is queued without COPILOT_API_KEY, matching memory cleanup. Workspace and workflow rows have no other hard-delete path: the UI archives them, and the soft-delete retention job already runs prepareChatCleanup for the workflows it purges. Autopsy: the account-removal integration suites asserted run stops, storage and memory cleanup, but no test looked at what the copilot backend kept for the chats the cascade erased. chat-backend-cleanup.integration.ts drives both removal paths against real PostgreSQL and a local backend fixture and asserts exactly the erased chats are purged; its account-deletion case fails on the previous code.

…and chat cleanup events Retention pruned completed rows of only two event types, so outbox_event kept every other completed row forever; the embedding checkpoint expiry events alone are most of the table. Completed rows older than the 7-day window are now also pruned for: - the three checkpoint expiry events. They are deterministic-id gates: a writer inserts the row before uploading and skips the upload once the row is no longer pending. The row completes at the checkpoint's 48-hour expiry, and after it is pruned the next writer of that key inserts a fresh pending cleanup before uploading, so no object is left without a cleanup. The new integration case drives writeFramedCheckpoint through completion, pruning and a rewrite to prove it. - workspace-file.live-doc.reconcile, workspace-file.storage.cleanup, mothership.memory.cleanup and copilot.chat.backend-cleanup: random ids, looked up only by the immediate post-commit process call while pending. Still kept: workflow deployment and workspace operation events (workspace operation receipts read their effect rows back by id and treat a missing row as a failed effect), enterprise/admin operation records, idempotency-keyed events, and every pending, processing and dead-letter row. The per-type batch and cadence are unchanged, so an existing backlog drains over successive maintenance runs.

…anup batch where the last ended The daily /api/webhooks/cleanup/idempotency run read the whole idempotency_key table four times for its before/after stats (count/min/max and a GROUP BY namespace, twice), which only fed two log lines and the cron response. It now reports what it actually deleted per namespace, counted from the delete's returned keys, and an estimated row count from pg_class.reltuples (one catalog read) after the sweep. The sweep itself started every batch from the oldest expired row. The global sweep keeps the permanent admin-credit-grant and workflow-execution-id claims, whose expired rows sit at the front of the created_at order forever, so each 1,000-row batch walked all of them again before finding anything to delete. Batches are now ordered by created_at and resume at the timestamp the previous successful batch ended on (>=, so keys sharing that timestamp are not skipped), and the retained rows are read once per run instead of once per batch. The new integration test sweeps expired keys across several small batches, including a tie on the boundary timestamp, and asserts every expired key goes while the permanent and fresh ones stay; it fails if the resume skips the tie.

…ooner Drop 32 b-tree indexes whose columns are a leading prefix of another non-partial b-tree on the same table, so the remaining index serves every lookup, range scan and foreign-key check they did. Each coverer is named beside its drop in the migration. Indexes whose only longer sibling is partial (user_table_def_workspace_id_idx, workflow_mcp_tool_server_id_idx) stay, since a partial index cannot serve FK checks. Lower the vacuum and insert-vacuum scale factors to 2% on embedding, workspace_files and copilot_async_tool_calls, which accumulate dead and unvacuumed rows well past the 20% defaults between runs. embedding_search is left alone: each vacuum there also scans its HNSW index.

…od stamps The period-sum read (entity plus both period stamps) bounded its scan on only three columns of the covering index, because user_id and created_at sat between the two stamps. With the planner also underestimating that match (the stamps are functionally dependent on the entity), it chose the slimmer index without cost and fetched every matched row from the heap. One index keyed (entity type, entity id, period start, period end, user_id) with created_at, source and cost as trailing payload now serves the period sums, the per-user sums, the weekly-refresh buckets and the cycle-close range index-only, and replaces both previous indexes. A replay after a failed build moves only an invalid copy of the new index aside to be dropped, so a valid index an earlier attempt built is kept rather than rebuilt.

…ndle The checkpoint-gate case added three more non-null assertions on the hoisted database holder. The suite now keeps the drizzle handle it builds and reads through it, so the file carries none and its explicit-any baseline entry goes.

…o and a pre-existing-behavior test useWorkspaceInvalidationRoom reads its callback through a ref and no effect lists it, so the folder tree's useCallback bought nothing. The cross-workspace broadcast test guarded a filter the coalescing change left untouched.

vercel · 2026-10-28T20:55:55Z

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

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Oct 28, 2026 11:32pm UTC

greptile-apps · 2026-10-28T21:01:25Z

Confidence Score: 5/5

[High impact] The PR appears safe to merge, with no new actionable issues found.

Summary

Reduces database work on busy reads and cleanup jobs, and records chat cleanup before deletion commits.

Audit-log lists page each scope separately and merge the results.
Chat and account deletion leave durable work to remove copilot data and unused files.
The database keeps fewer duplicate indexes and vacuums busy tables sooner.
Billing-period sums read their data from one covering index.
Connector reconciliation counts documents in bounded windows under its lease.
File-search backfill locks only files that still need a revision.
Idempotency cleanup resumes its batches and skips full-table statistics scans.
Outbox retention prunes completed cleanup events while keeping events read back by id.
Table changes look up active webhooks only in their workspace.
Deployed-state reads skip sending a cached state blob from the database.
Workspace file updates coalesce list refetches while one is already running.
Organization member removal follows the workspace-first lock order.
Checker baselines change without changing product behavior.

Diagram

sequenceDiagram
  participant Request as Chat delete
  participant DB as PostgreSQL
  participant Worker as Cleanup worker
  participant Storage as Backend and files
  Request->>DB: Lock chat and collect file keys
  Request->>DB: Record cleanup and delete chat
  DB-->>Request: Commit both together
  Worker->>DB: Read queued cleanup
  Worker->>DB: Check that chat is gone
  Worker->>Storage: Delete backend data and files
  Storage-->>Worker: Success or retryable failure

_{Reviews (6) · Last reviewed commit: "perf(billing): bound cycle close's previ..." · Reviewed by Greptile}

cubic-dev-ai

1 issue found across 61 files

Confidence score: 3/5

In reconciliation-window.ts, a count that reaches the deadline loses its cursor and accumulated totals, so the next sync starts counting from the first window again. Persist and resume the count progress.

Prompt for AI agents (unresolved issues)


Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="apps/sim/lib/knowledge/connectors/reconciliation-window.ts">

<violation number="1" location="apps/sim/lib/knowledge/connectors/reconciliation-window.ts:159">
P2: A count that reaches the deadline discards its cursor and accumulated totals, so the next sync recounts from the first window. Persist and resume the count progress; otherwise a connector that cannot be counted within one pass can remain unreconciled indefinitely.</violation>
</file>

_{This PR changes a database schema or migrates data. Ultrareviews find 2.4x more serious bugs than standard reviews. Comment @cubic-dev-ai ultrareview to run one.

Turn on auto-fix | Re-trigger cubic}

…del calls Reverts c921209. The cached admission it routed both calls through also caches the payer's billing-block result, so a payer blocked for payment after an admission was cached still passed for up to the cache TTL. The saved ledger sum per call was small next to that. The requestChatTitle test's cache reset existed only for that cached path and goes with it.

…with its delete A permanent chat delete purged the copilot backend and the chat's stored files after commit and only logged a failure, so a failed purge was lost: the chat row was gone and nothing could find it again. /admin/remove-user read the cascaded chats in its before hook and queued their backend cleanup in its after hook, logging either failure and letting the removal proceed with nothing recorded, and neither removal path purged the stored files of the chats it erased. The copilot.chat.backend-cleanup event now also carries the chats' stored-file keys, collected while the rows naming them exist (100 chat ids or 100 files per event). Its handler purges the backend data and deletes the objects of chats whose rows are gone, and throws on any failure, an already-missing object excepted, so the outbox retries; chat ids reaching a processor without COPILOT_API_KEY throw as the organization cleanup does. File events are queued even without the key. - deleteCopilotChat reads the keys under the chat row's lock and queues the event in its transaction, so the purge is recorded exactly when the delete commits; the post-commit best-effort purge is gone. - Account deletion reads the chats and keys before its transaction, as its storage sweep does, re-reads the chat ids under the account lock, reads the keys of chats created since, and queues it all in the transaction. - The admin remove-user before hook queues the event before the delete, due an hour later so the delete has committed; a failed read or enqueue throws, which makes Better Auth abort the delete. A delete that never happens leaves the chats alive, and the handler purges nothing for them. collectChatFiles moves to chat-files.ts so the auth graph does not load the backend and storage clients; it still adds five modules to the routes that import auth, and their module baselines are re-recorded. Autopsy: deletion.test.ts only asserted calls on a mocked prepareChatCleanup, so it could not see that the purge was not durable, and the integration stand-in accepted any request. The integration suite now drives the real chat delete, account deletion and admin hook against PostgreSQL, local storage and a stand-in that refuses anything but an authenticated POST /api/tasks/cleanup: a rolled-back delete records nothing, a failed backend call or object delete is retried until it succeeds, a missing key holds the backend purge, and a failed enqueue refuses the admin removal. Seven of its eight cases fail on the previous code.

…o not guarantee The per-window sums are not one snapshot. They differ from one only by the rows writers outside the sync lease change during the count, and they only gate whether a walk runs: every soft and hard delete re-checks absence in its own statement, as it already had to after the single count statement.

waleedlatif1 · 2026-10-28T21:35:15Z

@greptile

waleedlatif1 · 2026-10-28T21:35:16Z

@cubic-dev-ai review this PR

cubic-dev-ai · 2026-10-28T21:35:22Z

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

cubic-dev-ai

All reported issues were addressed across 60 files

_{Reply with feedback, questions, or to request a fix.

Turn on auto-fix | Re-trigger cubic}

…trigger, not any error

waleedlatif1 · 2026-10-28T21:46:18Z

@greptile

waleedlatif1 · 2026-10-28T21:46:19Z

@cubic-dev-ai review this PR

cubic-dev-ai · 2026-10-28T21:46:25Z

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

waleedlatif1 · 2026-10-28T21:46:40Z

@greptile

waleedlatif1 · 2026-10-28T21:46:42Z

@cubic-dev-ai review this PR

cubic-dev-ai · 2026-10-28T21:46:47Z

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

cubic-dev-ai

No issues found across 60 files

Confidence score: 5/5

Automated review surfaced no issues in the provided summaries.
No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}

Reverts 03ca9c5. A rollup holds entries in process memory until its window closes, so a minute-long window widens what a crashed process loses from the audit trail thirty-fold. Platforms that aggregate audit events summarize records already written durably; keep the short window.

waleedlatif1 · 2026-10-28T21:57:03Z

@greptile

waleedlatif1 · 2026-10-28T21:57:05Z

@cubic-dev-ai review this PR

cubic-dev-ai · 2026-10-28T21:57:11Z

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

cubic-dev-ai

No issues found across 58 files

Confidence score: 5/5

Automated review surfaced no issues in the provided summaries.
No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}

…lapsed period The covering usage_log period index added in 0441 has unique keys, so B-tree deduplication can't compress an entity's current period the way the old four-column index did, and max(billing_period_start) for the previous period walked every current-period entry first. The elapsed period starts before it ends, so bounding the start below it changes no answer and lets the scan skip the current period.

waleedlatif1 · 2026-10-28T23:31:56Z

@greptile

waleedlatif1 · 2026-10-28T23:31:58Z

@cubic-dev-ai review this PR

cubic-dev-ai · 2026-10-28T23:32:05Z

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

cubic-dev-ai

No issues found across 59 files

Confidence score: 5/5

Automated review surfaced no issues in the provided summaries.
No files require special attention.

_{You've manually re-run cubic several times on this PR. Each manual re-review checks the full PR again and counts toward your usage quota. To preserve your usage limits, we recommend letting cubic automatically review new commits.

Turn on auto-fix | Re-trigger cubic}

waleedlatif1 added 17 commits October 28, 2026 13:41

greptile-apps Bot reviewed Oct 28, 2026

View reviewed changes

Comment thread apps/sim/lib/mothership/chat/deletion.ts Outdated

Comment thread apps/sim/lib/mothership/chat/deletion.test.ts Outdated

vercel Bot deployed to Preview October 28, 2026 21:03

View deployment

cubic-dev-ai Bot reviewed Oct 28, 2026

View reviewed changes

waleedlatif1 added 3 commits October 28, 2026 14:14

cubic-dev-ai Bot reviewed Oct 28, 2026

View reviewed changes

Comment thread apps/sim/lib/cleanup/chat-backend-cleanup.integration.ts Outdated

Comment thread apps/sim/lib/auth/admin-removal-chat-cleanup.ts

chore(copilot): prove the cleanup rollback tests fail on the fixture …

99c0777

…trigger, not any error

vercel Bot temporarily deployed to Preview October 28, 2026 21:46 Inactive

docs(auth): state what the admin removal cleanup hook cannot cover

6e714dc

vercel Bot temporarily deployed to Preview October 28, 2026 21:46 Inactive

cubic-dev-ai Bot reviewed Oct 28, 2026

View reviewed changes

vercel Bot temporarily deployed to Preview October 28, 2026 21:57 Inactive

cubic-dev-ai Bot reviewed Oct 28, 2026

View reviewed changes

vercel Bot temporarily deployed to Preview October 28, 2026 23:32 Inactive

cubic-dev-ai Bot reviewed Oct 28, 2026

View reviewed changes

waleedlatif1 merged commit f2401ac into staging Oct 28, 2026
57 checks passed

waleedlatif1 deleted the perf/db-hot-paths branch October 28, 2026 23:40

This was referenced Oct 29, 2026

v0.9.37: dependency bumps, db improvements, ci fixes #9426

Open

fix(files): cap how long a room delivery waits for its refetches #9427

Merged

fix(cleanup): keep shared chat files, sweep inline images by prefix, and make room refetches wait #9433

Open

Conversation

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

Uh oh!

Summary

Type of Change

Testing

Checklist

Uh oh!

vercel Bot commented Oct 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

greptile-apps Bot commented Oct 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Confidence Score: 5/5

Summary

Diagram

Uh oh!

Uh oh!

Uh oh!

cubic-dev-ai Bot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

waleedlatif1 commented Oct 28, 2026

Uh oh!

waleedlatif1 commented Oct 28, 2026

Uh oh!

cubic-dev-ai Bot commented Oct 28, 2026

Uh oh!

cubic-dev-ai Bot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

waleedlatif1 commented Oct 28, 2026

Uh oh!

waleedlatif1 commented Oct 28, 2026

Uh oh!

cubic-dev-ai Bot commented Oct 28, 2026

Uh oh!

waleedlatif1 commented Oct 28, 2026

Uh oh!

waleedlatif1 commented Oct 28, 2026

Uh oh!

cubic-dev-ai Bot commented Oct 28, 2026

Uh oh!

cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

waleedlatif1 commented Oct 28, 2026

Uh oh!

waleedlatif1 commented Oct 28, 2026

Uh oh!

cubic-dev-ai Bot commented Oct 28, 2026

Uh oh!

cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

waleedlatif1 commented Oct 28, 2026

Uh oh!

waleedlatif1 commented Oct 28, 2026

Uh oh!

cubic-dev-ai Bot commented Oct 28, 2026

Uh oh!

cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

This branch was previously deployed

Reviewers

waleedlatif1 commented Oct 28, 2026 •

edited

Loading

vercel Bot commented Oct 28, 2026 •

edited

Loading

greptile-apps Bot commented Oct 28, 2026 •

edited

Loading

cubic-dev-ai Bot left a comment •

edited

Loading

cubic-dev-ai Bot left a comment •

edited

Loading