# New feature: Scheduled machines

**URL:** <https://community.fly.io/t/new-feature-scheduled-machines/7398>\
**Category:** General\
**Tags:** announcement\
**Created:** [September 23, 2022, 11:03pm UTC](https://community.fly.io/t/new-feature-scheduled-machines/7398 "2022-09-23T23:03:40Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![shugel](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/shugel/32/48662_2.png) [@shugel](https://community.fly.io/u/shugel)\
**Post date:** [September 25, 2022, 4:56pm UTC](https://community.fly.io/t/new-feature-scheduled-machines/7398/4 "2022-09-25T16:56:28Z")

</div>

Ahh, yep the second option worked – looks like I’ve got a new machine using the pushed image, and the `--schedule` switch was accepted, so I’ll find out if it runs sometime tomorrow.

So what’s the best approach to deploying updated images? It seems like you can’t / aren’t supposed to update machines with new images – just stopping it if necessary and removing it and creating a new one is preferred? How does that integrate with e.g. Github actions? If I understand correctly, I’d want to:

1. push the new image
2. deploy a new machine using the new ID
3. destroy the existing machine if the deploy is successful.

However for step 2 you’d need the image ID you just created, and for step 3 you’d need the current machine ID.

(Sorry, just thinking out loud here)

---

_[View the full topic](https://community.fly.io/t/new-feature-scheduled-machines/7398)._