--- title: "App Sleeping GA, Community Leaderboard, Canvas Improvements" date: 2024-02-09 number: 0172 url: https://railway.com/changelog/2024-02-09-app-sleep-ga --- # App Sleeping GA, Community Leaderboard, Canvas Improvements Is Railway good because it is Railway? Or is Railway, Railway because it is good? We don’t expect many people to get that reference. Anyway, App Sleeping is now Generally Available — a way to save on your usage where your app sleeps when there is no public network activity on your application. Server~~less.~~ To celebrate crossing $12,000+ in Template Kickback payouts, we are now making the act of making money on Railway into a e-sport. Want to know more? Scroll down. (In the meantime are working on a new Template Composer that will let you build arbitrarily complex templates [for fun and profit](https://railway.app/open-source-kickback).) So, without further ado, let’s get into the good stuff! ## App Sleeping GA After launch week and plenty of testing, we are now shipping App Sleeping to everyone. Infra Engineer, Miguel consumed 47 cans of a certain branded energy drink in the summer to get this out, the effects just now wore off. In case you just joined us for the ride: App Sleeping is a feature that will automatically stop your container if there is no outbound public network activity for 10 minutes. No special config, just flip a switch to turn it on so your workloads can turn off. Super useful for PR environments where you can save on cost of those environments. They turn back on just by making a request to them. *Note: by enabling App Sleeping, you are marking your workload as “deprioritized”. On remote cases, we may remove your workload from our servers requiring a re-build. * Bonus, services now display when they’re sleeping (if [App Sleeping](https://docs.railway.app/reference/app-sleeping) is enabled). Thanks to Engineer Evan who just joined us to fix this specific feature. [Image: Services now indicate when they are sleeping] ## Community Leaderboard It’s wonderful to witness the adoption of our community site as we co-create the forum with our community. We wanted a way for us to recognize our contributors and what better way to do that with ~~clout~~ social proof. As a result, Engineer Matt has been hard at work shipping our new Community Leaderboard. Say aloha to [the Community Leaderboard.](https://community.railway.app/leaderboard) Now, contributions on the platform are scored where you can get recognition for your hard work on the platform. …And there are multiple leaderboards! While we are here, we also want to thank everyone who’s been pushing the team to make our community site first class. [Image: A screenshot of our leaderboard in community.railway.app] *Lastly, the rumors are false, Railway is NOT pivoting into a battle-royale game where only the Top 10 contributors stay on the platform.* ## Services Quality of Life Improvements A massive nit mentioned by thousands of people now fixed. Services now display clearly the time at which they crashed. Evan also joined us to fix this issue as well. We hope he doesn’t hand in a resignation. [Image: Services now indicate the correct time at which they crashed] ## Plugin Migration Reminder We have migrated nearly 99.97 percent of all plugins on Railway to Databases. Great job everyone! We’re going to keep reminding you until the plugin deprecation date that [The Future of Databases is Services](https://blog.railway.app/p/launch-01-next-gen-databases) and that we have a beautiful [Migration Guide](https://docs.railway.app/guides/database-migration-guide#migration-process) you should check out. We are deleting all legacy database plugins on [February 23, 2024](https://docs.railway.app/guides/database-migration-guide#migration-timeline), so please make sure to migrate before then. If you have any questions, please [join the discussions in the Community Forum](https://community.railway.app/db-migration). ## Fixes and Improvements - We fixed an issue with timestamps on service crashes - Our party increases in strength, Evan joins Railway on our journey. - We fixed an issue with GitHub login - We reorganized settings for Volumes a little bit - We have shipped a new version of our network management software where we can gracefully handle re-connects more effectively. Blog post coming soon we promise.