Hello,

Would you mind sharing your use case on why you would like to have a health check run for more than ~15 minutes?

Either way, while the UI may only allow 999 you can set a RAILWAY_HEALTHCHECK_TIMEOUT_SEC variable to a value above what the UI allows you to.

https://docs.railway.app/reference/variables#user-provided-configuration-variables

Thanks; is there any way to have the env RAILWAY_HEALTHCHECK_TIMEOUT_SEC take precdence over the UI value? the UI doesn't allow me to clear out the value there, so it is overriding the variable that I set.

The use case for this is I'm running a Ponder indexer, which could take some time on startup before it is ready to serve requests. https://ponder.sh/docs/production/deploy

The variable should take precedence, is there any reason you think it's not?

We have another user running an indexer and they are extending their health check's via that variable far beyond what you can set in the UI.

The Retry Window in the logs reflects the UI's value which I cannot clear out, instead of the value of the variable that I set.

I had a previous value set in the UI that cannot be cleared, so it is taking precedence over the variable. If there is no value ever set in the UI, the variable works. I've verified this by creating a new environment

Ah gotcha, thanks for the information, I'll see what I can do to clear out that service setting for you either either Monday or Tuesday.

Though if it's faster for you, you could always recreate the service.

Update here, the health check in the service settings has been removed.

Please re-open if you are experiencing further issues for this topic!