@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.

@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.

@Kptainflintt you are welcome We are always delighted when we can quickly unblock a user!
Have a good day and don't hesitate to come back if you have other issues in the future.

@Kptainflintt Hey! XO team dev is doing a fix on it: https://github.com/vatesfr/xen-orchestra/pull/8979

FYI @pdonias

pdonias opened this pull request in vatesfr/xen-orchestra

closed fix(xo-server/resource-sets): only edit limits if `limits` is passed #8979

@olivierlambert I am asking XO Team about this issue.

@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.

@ph7 @coolsport00 thanks for the report, this topic will be adressed in our roadmap very soon.