Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion apps/web/src/app/(app)/data-exports/DataExportsClient.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -150,7 +150,7 @@ export function DataExportsClient() {
<CardDescription>
The export includes your App Builder project titles and the prompt prefixes recorded
with your usage history. Large accounts can take a while to generate. We&apos;ll email
you when it&apos;s ready, and downloads expire 7 days after that.
you when it&apos;s ready, and downloads expire 24 hours after that.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WARNING: New copy says downloads expire after 24 hours, but the backend still expires exports 7 days after completion

When an export completes, the user-data-export worker sets expires_at = now() + interval '7 days' (services/user-data-export/src/databases.ts:117), and the presigned download URL TTL is derived from that expires_at (services/user-data-export/src/index.ts, downloadExpiration). This PR changes only the UI copy, so after merge the page will tell users downloads expire in 24 hours while they actually remain available for 7 days. If the intent is a real 24-hour expiry, the worker change needs to ship with (or before) this copy; otherwise the copy should stay at 7 days. Note: the 24-hour figure matches the separate re-request throttle (apps/web/src/routers/user-exports-router.ts: "You can request one data export every 24 hours"), which is a different limit.


Reply with @kilocode-bot fix it to have Kilo Code address this issue.

</CardDescription>
</CardHeader>
<CardContent className="flex flex-col items-start gap-3">
Expand Down