Changing cron schedule is resetting num of replicas to 1

[pksunkara]

Changing cron schedule through API (or terraform provider) is resetting the num of service replicas to 1. The weird thing is that Railway allows us to set the num of replicas to 2 back again after the cron has been changed.

1. If cron is always supposed to have replicas set to 1: a. We need to add conflict rule when both replicas and cron settings are set. b. Railway needs to disallow changing num of replicas when cron is set.
2. If cron doesn't matter for num of replicas: a. Railway needs to not reset the num of replicas when changing cron.

@zuchka Please let me know which way to proceed.

Funding

• You can sponsor this specific effort via a Polar.sh pledge below
• We receive the pledge once the issue is completed & verified

[zuchka]

Hi--turned this into a ticket and passed to product team. Will hear more soon. thanks for this!