Skip to content

fix: allow one workspace export every 24 hours - #300

Merged
FrkAk merged 3 commits into
mainfrom
fix/daily-workspace-export-cooldown
Oct 16, 2026
Merged

FrkAk merged 3 commits into
mainfrom
fix/daily-workspace-export-cooldown

Conversation

@FrkAk

@FrkAk FrkAk commented Oct 16, 2026 •

Copy link
Copy Markdown
Owner

Summary

Task Reference: none

Shortens the workspace export cooldown from 30 days to 24 hours. The constant is now ORGANIZATION_EXPORT_COOLDOWN_HOURS, so the UI and error copy read "every 24 hours".

  • The 429 message also says when the next export is possible, from the same retryAfterSeconds as the retry-after header.

Type of change

  • Bug fix
  • New feature
  • Refactor / cleanup
  • Documentation

Testing

  • Tested locally with bun run dev
  • Linting passes (bun run lint)
  • Typecheck passes (bun run typecheck)
  • Workers smoke passes (bun run build:cf && bun run smoke:cf)

The cooldown route test covers the new window, the retry bound and the message.

Notes for reviewer

No migration: the window is evaluated at request time against existing organization_export_limits rows.

Docs impact

  • none

Compliance impact

  • content/legal/terms.md and content/legal/privacy.md still state one archive every 30 days; left unchanged since the new limit is more generous. Flagged for a follow-up decision.

@FrkAk FrkAk self-assigned this Oct 16, 2026
@FrkAk
FrkAk marked this pull request as ready for review October 16, 2026 13:05
@FrkAk FrkAk closed this Oct 16, 2026
@FrkAk FrkAk reopened this Oct 16, 2026
@FrkAk
FrkAk merged commit f2304ca into main Oct 16, 2026
7 of 11 checks passed
@FrkAk
FrkAk deleted the fix/daily-workspace-export-cooldown branch October 16, 2026 13:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant