added cron job to for daily failed email digest

[BilalG1]

Important

Add cron job and API endpoint for daily failed email digest with authorization and tests.

• Cron Job:
  • Added cron job in vercel.json to trigger /api/latest/internal/failed-emails-digest daily at midnight.
• API Endpoint:
  • New POST endpoint in route.ts to handle failed email digests, requiring STACK_CRON_SECRET for authorization.
  • Uses getFailedEmailsByTenancy from crud.tsx to fetch failed emails from the last 24 hours.
  • Sends email digest to tenant owners using sendEmail.
• Environment:
  • Added STACK_CRON_SECRET to .env.development for authorization.
• Tests:
  • Added tests in failed-emails-digest.test.ts for authorization and successful processing of failed emails.

^{This description was created by for c4ef137. You can customize this summary. It will automatically update as commits are pushed.}

[greptile-apps]

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

[vercel]

@BilalG1 is attempting to deploy a commit to the Stack Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
stack-backend	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 17, 2025 10:27pm
stack-dashboard	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 17, 2025 10:27pm
stack-demo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 17, 2025 10:27pm
stack-docs	❌ Failed (Inspect)			Jun 17, 2025 10:27pm

[recurseml]

😱 Found 2 issues. Time to roll up your sleeves! 😱

🗒️ View all ignored comments in this repo

• The constraint 'TokenStoreType extends string' is too restrictive. It should likely be 'TokenStoreType extends string | object' to match the condition check in line 113 where TokenStoreType is checked against {}
• Return type mismatch - the interface declares useUsers() returning ServerUser[] but the Team interface that this extends declares useUsers() returning TeamUser[]
• There is a syntax error in the super constructor call due to the ellipsis operator used incorrectly. Objects aren't being merged correctly. This syntax usage can lead to runtime errors when trying to pass the merged object to 'super()'. Verify that the intended alterations to the object occur before or outside of the super() call if needed.
• Throwing an error when no active span is found is too aggressive. The log function should gracefully fallback to console.log or another logging mechanism when there's no active span, since not all execution contexts will have an active span. This makes the code less resilient and could break functionality in non-traced environments.

📚 Relevant Docs

• Function sets backendContext with a new configuration but doesn't pass 'defaultProjectKeys'. Since defaultProjectKeys is required in the type definition and cannot be updated (throws error if tried to set), this will cause a type error.
• The schema is using array syntax for pick() which is incorrect for Yup schemas. The pick() method in Yup expects individual arguments, not an array. Should be changed to: emailConfigSchema.pick('type', 'host', 'port', 'username', 'sender_name', 'sender_email')

📚 Relevant Docs

• Creating a refresh token with current timestamp as expiration means it expires immediately. Should set a future date for token expiration.
• The 'tools' object is initialized as an empty object, even though 'tools' is presumably expected to contain tool definitions. This could cause the server capabilities to lack necessary tool configurations, thus potentially impacting functionalities that depend on certain tool setups.

📚 Relevant Docs

• 'STACK_SECRET_SERVER_KEY' is potentially being included in every request header without checking its existence again here. Although it's checked during initialization, this could lead to security issues as it's exposed in all communications where the header is logged or captured.

📚 Relevant Docs

• When adding 'use client' directive at the beginning, it doesn't check if file.text already contains the 'use client' directive. This could lead to duplicate 'use client' directives if the file already has one.

📚 Relevant Docs

[N2D4]

Good stuff!

[greptile-apps]

PR Summary

Added daily failed email digest functionality with cron job and secure API endpoint to notify tenant owners of delivery issues.

• New internal endpoint /api/latest/internal/failed-emails-digest with STACK_CRON_SECRET authorization
• Raw SQL query in apps/backend/src/app/api/latest/internal/failed-emails-digest/crud.tsx using dynamic parameters without proper object safety
• Vercel cron job configured to run daily at midnight
• E2E tests in apps/e2e/tests/backend/endpoints/api/v1/internal/failed-emails-digest.test.ts verifying authorization and email processing
• Environment variable STACK_CRON_SECRET added to .env.development for local testing

_{5 files reviewed, 1 comment
Edit PR Review Bot Settings | Greptile}

[N2D4]

Feel free to merge when tests pass!