Reviewing files that changed from the base of the PR and between 48a233e and 5a066c5.

• apps/web/app/(ee)/api/admin/links/route.ts (1 hunks)
• apps/web/app/(ee)/api/cron/domains/delete/route.ts (4 hunks)
• apps/web/app/(ee)/api/cron/domains/transfer/route.ts (1 hunks)
• apps/web/app/(ee)/api/cron/domains/update/route.ts (1 hunks)
• apps/web/app/(ee)/api/cron/folders/delete/route.ts (1 hunks)
• apps/web/app/api/domains/route.ts (1 hunks)
• packages/prisma/schema/link.prisma (1 hunks)

packages/prisma/schema/link.prisma (2)

91-91: Well-designed composite index for bulk operations.

The new [domain, createdAt] index is correctly structured with domain as the leading column for filtering and createdAt for efficient ordering in the bulk deletion workflows.

---

93-93: Improved documentation for existing index.

The expanded comment better documents the multiple use cases for the userId index, improving code maintainability.

apps/web/app/(ee)/api/cron/domains/update/route.ts (1)

41-43: Excellent use of the new composite index.

Adding createdAt: "desc" ordering prioritizes processing of recently created links, which improves user experience for recent domain changes. This query will efficiently leverage the new [domain, createdAt] index.

apps/web/app/api/domains/route.ts (1)

47-49: Minor query optimization through filter reordering.

Reordering the domain filter before the key filter is a good practice as domain is likely more selective than checking for just two specific key values.

apps/web/app/(ee)/api/cron/domains/transfer/route.ts (1)

32-34: LGTM! Consistent ordering for transfer operations.

The addition of orderBy: { createdAt: "desc" } ensures consistent processing order and prioritizes more recent links during transfer operations, which aligns with similar changes across other cron routes.

apps/web/app/(ee)/api/cron/domains/delete/route.ts (5)

3-3: Good addition of rate limiting capability.

Adding the limiter import enables proper rate limiting for storage operations, which is implemented well in the R2 deletion logic below.

---

46-49: LGTM! Consistent ordering pattern.

The addition of take: 100 and orderBy: { createdAt: "desc" } maintains consistency with other cron routes and ensures predictable processing order.

---

52-52: Helpful logging for monitoring.

The console log provides useful visibility into the deletion process.

---

68-72: Excellent rate limiting implementation for storage operations.

Using limiter.schedule() for R2 deletions prevents overwhelming the storage service and is a best practice for bulk operations.

---

112-131:

Details

❓ Verification inconclusive

Critical functionality is disabled - verify if intentional.

The commented-out code disables two essential features:

1. Re-queuing domain deletion jobs when links remain (lines 112-120)
2. Final domain and logo deletion after all links are processed (lines 122-131)

This fundamentally changes the behavior from actually deleting domains to only deleting links. The response message still claims "Domain deleted" (line 134) but the domain isn't actually removed.

Please confirm if this is intentional (e.g., for testing/debugging) or if this code should be re-enabled:

---

🏁 Script executed:

#!/bin/bash
# Check if there are any related tests or documentation about this change
rg -A 5 -B 5 "queueDomainDeletion|Domain deleted" --type ts

Length of output: 3636

---

Verify intentional removal of domain deletion and re-queuing

The cron route’s logic for

• re-queuing remaining link batches (formerly lines 112–120) and
• deleting the domain record and its logo (formerly lines 122–131)

is currently commented out. This means only the links are ever deleted, yet the response still claims “Domain deleted.”

Please confirm whether this change was intentional (e.g., for testing/debugging or a phased rollout). If not, you should:

• Re-enable queueDomainDeletion when remainingLinks > 0
• Restore the final prisma.domain.delete and storage.delete calls once all links are processed
• Update the response message to reflect actual behavior
• Add or update tests covering the cron deletion workflow