Having looked into this, the issue appears to be in your application code or configuration rather than the Railway platform itself, which puts it outside what Railway support can resolve directly.

This is exactly the kind of problem the Railway community is good at, so we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who solves it, and threads like this usually get picked up quickly.

Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.

• Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
• Keep it private and close the thread - Nothing becomes public. The thread closes, since this isn't something Railway support can take further.

Click the purple Regenerate credentials and redeploy button located within that warning box.

It cannot be from our application code

I have done this, but the problem not solved

Do this if the deployment remains stuck or the PITR state does not recover,

1. Click stage disable button and Redeploy. (Removes the stuck PITR)
2. Re Enable PITR again once it's disabled.
3. If PITR recreates the archive successfully, then you're good to go. Otherwise regenerate credentials and redeploy last time.

Postgres should be allowed to redeploy automatically after enabling.