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.

What is this bot doing??

This is pure nonsense! I'd open it to the community, but i don't want information about our railway service leaked, which i selected on thread creation.

Apologies for the earlier bot response - this is a platform configuration issue we can help with directly. The env var to disable Railpack's mount caches is RAILPACK_DISABLE_CACHE (singular), not RAILPACK_DISABLE_CACHES with a trailing S. The variable you set was silently ignored, so the .next/cache mount cache (where Next.js stores fetched CMS data between SSG builds) was never cleared. NO_CACHE=1 only disables build layer caching, which is why you saw "Caching disabled" but pages still built instantly from stale cached fetch results. Set RAILPACK_DISABLE_CACHE=* and redeploy to force a full refetch of all your SSG pages.

Not cool, bot! That typo was not the issue!

This still looks like an application-level problem, so Railway support can't take it further, but the community can. The buttons below are still live: open the thread up as a public bounty after editing out anything sensitive, or keep it private and close it.

Hey, the service has been running in production for over a year. Suddenly, it can no longer deploy with fresh data.

All options to disable cache are NOT working! They are either functionally broken or misdocumented. A fresh deploy in a test environment needed almost 10 minutes to build overall.

With ALL Caches DISABLED, this service is still redeploying within 2 minutes, while the actual npm build takes only SECONDS. NO FETCHING of fresh data happening. If anyone wants to tell me, that the Railpack Cache can be disabled, it is simply NOT TRUE!

Where the error is, if it is in Railway, on the cms or somewhere else outside Railway, i cannot say with absolute certainty, but the disabling of CACHE would have been a temporary solution in any case - BUT IT DOES NOT WORK.

Also, i asked the following questions without any answer:

1. When i open this thread to the community, do the information about our linked private Railway service get leaked to the public? (i will happily open to the community if not)
2. I wanted to know, whether it is possible to downgrade Railpack?

We are on a paid plan and i am expecting some kind of support for a big multi-tenant production application with over 10 of our customers connected to it.

If this is the wrong spot to ask for support, please tell me what else we should do!

But don't silent this thread again with this incompetent AI slop!

This is unprofessional!

Regards

This still looks like an application-level problem, so Railway support can't take it further, but the community can. The buttons below are still live: open the thread up as a public bounty after editing out anything sensitive, or keep it private and close it.

Hi there.

Sorry for the inconvenience this issue has caused you.

This could be an application level caching rather than railway caching. May i know what SSG framework you are using?

Also could you please confirm if Skipped builds is not enabled.

You can check from: Service Settings → Feature-flags → Skipped Builds