fix: increase realtime createdAt filter max from 24h to 7d

[kaigritun]

Summary

Increases the REALTIME_MAXIMUM_CREATED_AT_FILTER_AGE_IN_MS default from 24 hours to 7 days.

Problem

When using useRealtimeRunsWithTag with createdAt: '1w', runs older than 24 hours are silently excluded because the server caps the filter to REALTIME_MAXIMUM_CREATED_AT_FILTER_AGE_IN_MS (default 24h), regardless of what the client requests.

This causes confusion when monitoring long-running jobs that have been in progress for more than a day - they simply don't appear in the realtime hook despite being visible in runs.list and the dashboard.

Solution

Increase the default cap from 24 hours to 7 days to match common user expectations. Users requesting createdAt: '1w' will now see runs from the past week as expected.

The environment variable remains configurable for deployments that need stricter limits.

Changes

• apps/webapp/app/env.server.ts: Change default from 24 * 60 * 60 * 1000 to 7 * 24 * 60 * 60 * 1000

Fixes #3018

---

[changeset-bot]

⚠️ No Changeset found

Latest commit: a24ec97

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request updates a single configuration constant in the environment schema file. Specifically, the default value for REALTIME_MAXIMUM_CREATED_AT_FILTER_AGE_IN_MS is increased from 24 hours to 7 days. This is a straightforward configuration adjustment with no accompanying changes to validation logic, control flow, or other related code.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2feecec and a24ec97.

📒 Files selected for processing (1)

• apps/webapp/app/env.server.ts

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Hi @kaigritun, thanks for your interest in contributing!

This project requires that pull request authors are vouched, and you are not in the list of vouched users.

This PR will be closed automatically. See https://github.com/triggerdotdev/trigger.dev/blob/main/CONTRIBUTING.md for more details.

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.