It’s possible that this is an intended cold start behavior. Websockets usually have challenges when synchronizing data to Cloud Run because instances are stateless while websockets are stateful.

When it comes to choosing between first and second generation of Cloud Run, both will still discard in-memory data once an instance is terminated or scaled down. But in terms of cold start times, the first generation has faster cold start times than the second generation.

You can also try setting a minimum number of instances to reduce the cold start time.