Skip to content

fix: poll GetProject while hibernating so waking auto-redirects#9558

Closed
nishantmonu51 wants to merge 1 commit into
mainfrom
nishant/fix-hibernation-resume-stuck
Closed

fix: poll GetProject while hibernating so waking auto-redirects#9558
nishantmonu51 wants to merge 1 commit into
mainfrom
nishant/fix-hibernation-resume-stuck

Conversation

@nishantmonu51

Copy link
Copy Markdown
Collaborator
  • A hibernated project has no deployment, so GetProject's refetchInterval returned false and disabled polling entirely.
  • The only bridge out of the hibernating screen was the single refetchQueries in RedeployProjectCTA. If that one refetch raced ahead of the backend's visible state (the redeploy does several DB writes; read-replica lag is realistic), polling never re-armed and the UI stayed stuck on the "Waking…"/provisioning screen.
  • Now refetchInterval keeps polling (every 2s) while a loaded project has no deployment, so the layout auto-progresses to provisioning → project home once a deployment appears, whether woken from this tab or another session. Error/empty states still return false.
  • Polling a hibernating project is safe: GetProject only marks a deployment "used" when one exists, so it doesn't reset hibernation timers.

Checklist:

  • Covered by tests
  • Ran it and it works as intended
  • Reviewed the diff before requesting a review
  • Checked for unhandled edge cases
  • Linked the issues it closes
  • Checked if the docs need to be updated. If so, create a separate Linear DOCS issue
  • Intend to cherry-pick into the release branch
  • I'm proud of this work!

Developed in collaboration with Claude Code

A hibernated project has no deployment, so the GetProject query's
refetchInterval returned false and disabled polling. The only bridge out
of the hibernating screen was a single refetch in RedeployProjectCTA; if
it raced ahead of the backend's visible state, polling never re-armed and
the UI stayed stuck on the "Waking..."/provisioning screen.

Keep polling while a loaded project has no deployment so the layout
auto-progresses to provisioning and then the project home once a
deployment appears, whether woken from this tab or elsewhere.
@nishantmonu51

Copy link
Copy Markdown
Collaborator Author

Closing, in favor of new PR.

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.

2 participants