{"_id":"55d3b64af77e6d0d00b1b2a2","category":{"_id":"55d3b645f77e6d0d00b1b276","version":"55d3b644f77e6d0d00b1b273","__v":1,"project":"55c505b41469ad2500fa2ab7","pages":["55d3b64af77e6d0d00b1b29f","55d3b64af77e6d0d00b1b2a0","55d3b64af77e6d0d00b1b2a1","55d3b64af77e6d0d00b1b2a2"],"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-08-10T18:44:12.108Z","from_sync":false,"order":3,"slug":"triggers","title":"Triggers"},"parentDoc":null,"__v":0,"user":"55c50f4a7c199a2f00665cbf","version":{"_id":"55d3b644f77e6d0d00b1b273","project":"55c505b41469ad2500fa2ab7","__v":6,"createdAt":"2015-08-18T22:48:36.632Z","releaseDate":"2015-08-18T22:48:36.632Z","categories":["55d3b645f77e6d0d00b1b274","55d3b645f77e6d0d00b1b275","55d3b645f77e6d0d00b1b276","55d3b645f77e6d0d00b1b277","55d3b645f77e6d0d00b1b278","55d3b645f77e6d0d00b1b279","55d3b645f77e6d0d00b1b27a","55d3b645f77e6d0d00b1b27b","55d3b645f77e6d0d00b1b27c","55d3b645f77e6d0d00b1b27d","55d7c2939510f00d007ec6fe","56fac9925df15a20002972a2","56fb2f7668e1d30e00a0b672","583498d411e8af2500f6b334","58e52a180ab7b03b00f4a97a"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"1.1.0","version":"1.1"},"project":"55c505b41469ad2500fa2ab7","updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-08-10T23:08:08.255Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":3,"body":"You can schedule a cron job on Neptune and configure an action that needs to be run when a cron is triggered. This helps you to avoid running crons local machines where there is risk of missing cron if the host is down.\n\nCron triggers are a very good use case for shutting down resources at the end of a day, shutting down test machines at end of a week, auto scaling your infrastructure or heroku dynos at the same time every day based on the load on your application.\n\nWe are also working on use cases to support executing distributed cron actions on:\n* Exactly one machine from a host group\n* At least n machines in a host group\n* All machines in a host group.\n\nPlease get in touch with [support](mailto:support:::at:::neptune.io) if you have any specific use cases that we don't support yet.","excerpt":"","slug":"cron-triggers","type":"basic","title":"Cron Triggers"}
You can schedule a cron job on Neptune and configure an action that needs to be run when a cron is triggered. This helps you to avoid running crons local machines where there is risk of missing cron if the host is down. Cron triggers are a very good use case for shutting down resources at the end of a day, shutting down test machines at end of a week, auto scaling your infrastructure or heroku dynos at the same time every day based on the load on your application. We are also working on use cases to support executing distributed cron actions on: * Exactly one machine from a host group * At least n machines in a host group * All machines in a host group. Please get in touch with [support](mailto:support@neptune.io) if you have any specific use cases that we don't support yet.