Your workspace is on the Hobby plan, where volume backups and PITR are not available. The Hobby plan's backup limit is set to zero, which is why the Backups tab loads empty and the API returns "Not Authorized." These features are available on the Pro plan.

Hello Railway Support,

Following your reply, we upgraded the workspace to the Pro plan.

Post-upgrade verification:

• Scheduled volume backups are now successfully configured (Daily, Weekly, and Monthly).
• A manual backup and restore drill completed successfully (PASS).
• PostgreSQL 18.4 is operational and accepting connections.
• The staging PostgreSQL volume is operational.

The only remaining issue is PITR: the Backups page for the existing staging PostgreSQL service still does not display the “Enable PITR” control.

Affected staging service:

• Project: mindujo-tessera-oro-demo
• Environment: staging-v1
• Service ID: 1087b9cf-e7b5-408d-baf3-309cb91c6c39
• Volume ID: 8c88b1fe-85a0-424d-8bbc-54cc197ccad2

Could you please verify the PITR entitlement/control for this existing staging PostgreSQL service and enable it, or provide the exact required action if a support-side change is necessary?

No Production environment or customer data is involved. This remaining PITR issue is blocking final staging qualification.

Thank you.

Hello Railway Support,

We completed a fresh read-only verification after the Pro upgrade:

• the authenticated workspace session and Railway API both report the Pro plan;
• PostgreSQL uses the supported major image tag ghcr.io/railwayapp-templates/postgres-ssl:18 and is running PostgreSQL 18.4;
• the database and restored existing volume are operational;
• scheduled backups are configured and the volume restore drill passed;
• the service Backups view still does not render the “Enable PITR” control and produces React hydration/rendering errors (#418 and #423);
• the alternative volume view exposes only Metrics and Settings.

Railway's PITR documentation does not list any additional prerequisite for PostgreSQL 18 or for an existing volume that is missing from this staging service.

Does enabling PITR require manual intervention on our project after the upgrade?

Please verify the PITR entitlement/UI for staging service 1087b9cf-e7b5-408d-baf3-309cb91c6c39 and advise or apply the required support-side action.

No Production environment or customer data is involved.

Thank you.

Hello,

I'm following up on our existing ticket 911535d8.

Since the previous update:

• our Railway workspace has been successfully upgraded to Pro;
• scheduled backups are now available and configured;
• the PostgreSQL staging service is operational;
• PostgreSQL 18.4 has been validated successfully;
• a manual restore drill has been completed successfully.

However, the Enable PITR control is still not available in the PostgreSQL service UI.

We have already verified:

• a new login/session after the upgrade;
• alternative PostgreSQL service views;
• no documented prerequisites missing for PostgreSQL 18.4 or existing volumes.

The issue still persists.

At this point this is the only remaining blocker preventing completion of our staging qualification and the release path of our application.

Could you please verify whether:

• PITR must be manually enabled on our project,
• there is a backend authorization issue,
• or there is a UI issue affecting our workspace?

Please continue using ticket 911535d8.

Thank you very much.

Hi, sorry about that, I've just merged a fix for this, it should finish deploying soon.

Basically it wasn't loading in some screens due to a race condiiton + a screen size check combining.