please provide the logs that show that the error

https://bookmarklets.up.railway.app/log-downloader/

Here's the log

Also seeing this issue.

okay thanks for the reports and the log, I will look into it.

fixed in this PR

Until this is merged you may deploy your service from the branch in my PR.

Edit: PR has been merged

fixed in this PR

Until this is merged you may deploy your service from the branch in my PR.

Thanks! Is it usually pretty fast to get PRs like these merged? Asking since I think otherwise we'd have to fork the template repo first to be able to deploy from your PR branch – since the GitHub integration only lets us pick from personal & organization repos we've got direct access to, not public stuff. (Or I'm missing something obvious.)

yeah as far as I know you would have to fork my repo and its branches to be able to deploy my PR branch.

though I have asked the team to look at the PR.

let me take a look at the PR rn

We've merged Brody's PR! thank you Brody!

Let us know if you experience any further issues.

Thanks everyone for the quick turnaround! How do I get the service to pick up the changes, by the way? Railway seems to be reporting the upstream is "up-to-date", even though I can see the PR was in fact merged. (I know I can recreate the service entirely but this seems like a good thing to figure out in case there are future updates.)

Hm interesting.. can you try a Redeploy?

the check for updates feature has a tendency not to work, so if the redeploy doesn't work what I would do is -

• remove both the source and upstream repositories from the service.

• delete your cloned repository.

• fork the template's repository - https://github.com/railwayapp-templates/postgres-s3-backups

• connect that newly forked repository to your service.

then it will deploy the newly updated repository, and for any future updates, simply watch Railway's repository, when there's a PR merged you can easily go back to your fork and click the sync button and Railway will deploy the changes.

Yep, makes sense – just nuked & recreated the service (and cloned repo) and it seems to be happy now. Thanks again.

no problem!