@CodeMercenary hello and thanks for this idea! We will discuss about it with @clemencebx and see what we can propose on new XO-6 design and workflow.

@hanzzz Hello, indeed I agree that we need to add this to the hosts actions to handle by REST API.
Let's add this to our futures features on the REST-API

FYI @MathieuRA

@Pilow @olivierlambert the "stacked" tags are already in our Design System :

Just a little patience, it will happen in 2026

@flakpyro yes, indeed that exactly what I was talking about. The XO6 new interface will provide more information, but I am noting the missing type of bound to discuss it with XO team for next feature.

@ph7 Hello, XO-6 does not yet support reactivity in data retrieved by the API, so you have to reload the page to get the updated information. This is in the pipeline and will arrive very soon.

@acebmxer Hello,

We’re aware of the Backblaze rate limits and this isn’t the first time it’s been raised. We’ll be looking into this on the XO side, studying different options such as caching restore points to reduce API calls. Longer-term improvements, possibly tied to advanced XO6 dashboards, are more of a 2026 horizon.

Thanks for bringing this up!

@McHenry hello, thanks for the report.
Can you open a suggestion on Github so we can plan it or next roadmap?
Have a good day.

@olivierlambert transfered

Hello @manilx and thanks for your reply.
I am asking the XO Team and will keep you in touch.

@JoaoL Hello and thanks for the information. I'll inform the XO team.

@ph7 that's fine, keep on testing our new XO-6, we are very happy with all our community feedback

@edsilber After exploring the UI, I confirmed that it's not possible to schedule a one-time cron job from the XO-5 interface.

We're prioritizing the development of new features for XO-6, so we'll take your suggestions regarding scheduling into account for the new interface.

I propose an alternative: using the REST API to run schedules by creating your own execution script (if you are on linux: https://www.veeble.com/kb/scheduling-one-time-jobs-in-linux-using-at-command/).

The REST API link is: {your-xo-url}/rest/v0/docs/#/schedules

Please feel free to contact me if you have any further questions.

@edsilber Hello and thank you for your help! I'm currently reviewing the user interface and discussing it with the XO team. I'll get back to you as soon as I've found the best way to help you…

@ph7 XO-Lite and XO-6 are 2 differents projects, so no they are not using the same code, even if the UI looks similar... ^^"

@ph7 hello and thanks for your reply.

The current XO-6 form is not yet finalized... we are still working on it. An informational message will be added to indicate what will and will not be possible to manage in this version of the form. The final version is planned for early 2026, and we are working as quickly as possible to provide all users with the best possible experience on this VM creation form.

We apologize for any inconvenience and will do our best to minimize it.

@kagbasi-ngc hello! For now the token has to be added in cookie, why do you need to send it by url?

@Pilow I know, it is like waiting for the part 2 of your favorite movie saga...

As @olivierlambert said, we will do our best to release this in early 2026, but we have plenty of interesting topics to come on XO-6

@Pilow @olivierlambert the "stacked" tags are already in our Design System :

Just a little patience, it will happen in 2026

@ph7 Hello, XO-6 does not yet support reactivity in data retrieved by the API, so you have to reload the page to get the updated information. This is in the pipeline and will arrive very soon.

@vmpr hello, to be able to address the problem more clearly can you give me the version of your XO please? and if you are on stable or latest? XO v5.111.0 has been publicly released in latest channel yesterday.