I have an existing app that’s hitting the default concurrency limits. I updated the limits in fly.toml, a new version of the app deployed, but I still see the limit warning on the monitor logs:
[services.concurrency]
hard_limit = 250
soft_limit = 200
type = "requests"
I checked with fly config display -a starrail to confirm that the toml is read correctly:
But I’m still getting the warning on the old 25 connection limit:
sea [warn] Instance *** reached hard limit of 25 concurrent connections. This usually indicates your app is not closing connections properly or is not closing them fast enough for the traffic levels it is handling. Scaling resources, number of instances or increasing your hard limit might help.
Is there something else I need to do for the updated concurrency limits to take?