Use the To-Do Center to fix what needs you across your sites and servers in xCloud

Updated November 22, 2026 · 10 min read

Summarize with:
Share:

The To-Do Center is one list of everything that needs you across your xCloud servers and sites. Each problem is a card with its own buttons, so you can fix it, ask the AI assistant why it happened, or put it off, without opening each server and site to look for notices. It is available to every xCloud team.

Watch the To-Do Center in 35 seconds: a PHP security patch fixed on 6 servers from one card, Fix with AI on a site, and the Done tab with every fix.

Open your To-Do list

Your list is one click away from any page in the dashboard, and the Overview page shows the most urgent items.

Step 1: Open the list

Click the to-do list icon in the top bar. The red number shows how many items are open. On the Overview page, you can also click Review all in the Needs your attention box.

Click the to-do list icon in the top bar of the xCloud dashboard to open Your to do

The Your to do panel opens on the right side of the page.

Step 2: Read the tabs and labels

The panel has four tabs:

  • ToDo: everything open now, most urgent first.
  • Ignored: cards you chose to hide for now.
  • Done: what was fixed in the last 30 days, and by whom.
  • Docs: guides for the page you are on.

The ToDo, Ignored, Done and Docs tabs at the top of the Your to do panel

Each card carries one of three labels: Important, Needs attention or Recommended. One card can cover many sites or servers, with a row for each. Click a site or server name to open the page that shows the problem. Your list updates by itself: xCloud checks every 15 minutes, and a card usually closes as soon as xCloud sees the problem is gone.

WordPress plugin, theme and core updates

What you see: “WordPress updates are waiting on 3 sites”, with one row per site. A site is added as soon as Update Manager finds updates on it, and the card counts the same sites Update Manager does, so the two numbers match. Must-use and drop-in plugins are not counted on either.

Buttons: Fix with AI, How to fix, Snooze, Ignore, and Skip on each row. This card has no one-click Fix button, because xCloud leaves the choice of what to update with you.

What happens: Click Fix with AI. The assistant lists the waiting updates and checks for a backup from today. It recommends a backup first if there is none, then updates only what you approve. It re-checks the site afterwards.

The assistant reports each update when it finishes. If an update fails or is skipped, the chat says Update failed on that site with the reason. If an update that looked failed finishes late and works, the assistant posts a correction, so the chat matches what happened on the site.

Click ‘Fix with AI’ on the card that says WordPress updates are waiting on 3 sites

The assistant opens beside your list with the card’s problem already filled in. Back to To-Do returns you to the list.

The xCloud AI Assistant open on a Fix with AI request, with the Back to To-Do link at the top

To update by hand instead, click a site name to open its updates page. Manage and update WordPress core and themes covers that page.

A PHP security patch

What you see: “A PHP security patch is needed on 1 server”, labelled Important. It appears when a critical PHP vulnerability affects a server and a patched release is ready.

Buttons: Fix (or Fix all for several servers), Fix with AI, How to fix and Snooze. There is no Ignore, and Snooze only offers 1 day. The one exception is a row you can skip on some Ubuntu 20.04 servers, below.

What happens: Click Fix, read the confirmation, then click Fix now. xCloud updates the installed PHP versions on that server. Your sites stay online, and it takes about 2 to 5 minutes per server.

This card is for security patches. A site on an older PHP version does not get a card just for its version.

A server on Ubuntu 20.04

This applies to Nginx servers on Ubuntu 20.04. An OpenLiteSpeed server on Ubuntu 20.04 can still be patched as usual. Its row keeps Fix, or Retry if a try did not work, and it has no Skip.

What you see: once xCloud has tried to patch the server and cannot, the row says “Your server runs Ubuntu 20.04, which no longer gets PHP security builds. We cannot patch PHP on it. Move your sites to a server with Ubuntu 22.04 or 24.04.” Before xCloud has tried to patch the server, the row shows the normal Fix button. Once the warning appears, the row has no Fix and no Retry. When every server left on the card shows this warning, the card also leaves out Fix with AI and How to fix. The card’s own text then says the same thing.

Click ‘Skip’ on a server row that says it runs Ubuntu 20.04 and cannot be patched

What to do: create a new xCloud server with Ubuntu 22.04 or 24.04. Migrate all sites between two xCloud servers moves every WordPress site in one run. Once your sites work on the new server, delete the old server in xCloud. Its row then leaves the card.

If you can’t move yet: click Skip on the row. Unlike other PHP patch rows, an Ubuntu 20.04 row can be ignored this way. The row stays on the card with a Restore link until the other servers on the card are fixed. When no other server is left to fix, the card moves to the Ignored tab and keeps its warning there, because PHP on the server is still not patched. The row stays skipped until xCloud can patch the server or a new PHP security fix comes out. It comes back with the normal Fix button, so click Fix to try again. To bring it back sooner, click Restore on the row. The row then still shows the warning and has no Fix.

Click ‘Restore’ on the Ubuntu 20.04 server row in the Ignored tab to bring it back to your list

Plugin and theme vulnerabilities

What you see: “1 site has known vulnerabilities”, with one row per affected site.

Buttons: Fix with AI, How to fix, Snooze, Ignore, and Skip on each row.

What happens: Click Fix with AI. The assistant starts from the scan xCloud already ran, so it does not scan each site again. For each finding, it names the plugin or theme, the installed version and the version that fixes it.

It then asks you once per site, listing exactly which plugins and themes it will update and the versions they will reach. It updates only the ones that have a fixed version. If no fixed version exists, it says so and suggests deactivating the plugin or theme from WordPress. It never ignores a vulnerability for you.

After you approve, the assistant tells you the updates have started and waits for them to finish. It then reports each plugin or theme as updated, failed with the reason, or skipped, and checks the site’s scan again to confirm the vulnerability is gone. It hands you over to support if there are signs the site is being attacked, or if no safe version exists.

Click ‘Fix with AI’ on the card that says 1 site has known vulnerabilities

Click the site name to see the scan results yourself. The vulnerability checker guide explains them.

Modified WordPress files

What you see: “Modified WordPress files found on 1 site”, with one row per site. It appears when WordPress core or plugin files on a site are different from the official release. That can mean a hack or a bad update.

Buttons: Snooze and Ignore on the card, and Skip on each site’s row. Click the row’s Review files link to open the site’s Integrity Monitor and see which files changed. Verify WordPress checksums explains that page.

Skip a site: click Skip on its row. The row is hidden for 7 days. If the files are still different after that, the row comes back.

Skipping here does not hide the site’s own modified files alert. That alert has its own Ignore button. Restore on the row brings back the To-Do row only, and leaves the site alert as it is.

A WordPress fatal error

What you see: “WordPress logged a fatal error on 1 site”, labelled Important. The cause is usually a plugin or theme.

Buttons: Ask AI why, How to fix, Snooze, Ignore, and Skip on each row. This card has Ask AI why rather than Fix with AI, because the cause has to be found first.

What happens: Click Ask AI why. The assistant reads the site’s error log and names the plugin, theme or file behind the error.

Click ‘Ask AI why’ on the card that says WordPress logged a fatal error on 1 site

If an update exists, the assistant offers it. If not, it suggests deactivating that plugin from WordPress. It asks before any update, and it reads the log again afterwards to see whether the errors stopped.

The xCloud AI Assistant open on an Ask AI why request about the WordPress fatal error

Prefer to look yourself? Click the site name to open its debug log, then follow how to troubleshoot “There has been a critical error”.

Failed backups, SSL, disk, CPU, services and disconnected servers

These cards explain what is wrong and link the guide for it. Most of them need you to find the cause first, so they offer Ask AI why and How to fix.

Card When it appears AI button Guide
Backups are failing The latest scheduled backup did not finish Ask AI why Backup failures
SSL failed or SSL certificate expires soon A certificate failed, or is close to expiring Ask AI why Failed free SSL
Disk space is running low Less than 5 GB is free Ask AI why Reclaim disk space
CPU has been high for a while Sites on the server may be slow Ask AI why Server at 100% CPU
A required service is down A service your sites need has stopped Fix with AI Manage services
Server cannot be reached xCloud has lost contact with the server Ask AI why Server disconnected

For example, a failed backup means there is no fresh copy to restore. Click Ask AI why to have the assistant look into it.

Click ‘Ask AI why’ on the card that says Backups are failing on 1 site

A stopped service is the one card in this group with Fix with AI. The assistant checks why the service stopped and asks before it starts or restarts it. A required service is down and Server cannot be reached can be snoozed but not ignored, because your sites may be offline.

Click ‘Fix with AI’ on the card that says a required service is down on 1 server

Operating system updates and the NGINX upgrade

These two cards can be fixed directly from the list. Fix works on one row, and Fix all (N) works on every row you can fix.

Every Fix opens a confirmation first, so you can see What changes, Downtime and Time before anything runs. Click Fix now to start, or Cancel to go back.

Click ‘Fix now’ after reading What changes, Downtime and Time for the security updates on a server

  • Security updates are waiting: installs the waiting security updates and restarts the server if they need it. Expect a short restart, usually under a minute, when a reboot is required. It takes about 5 minutes per server. The card counts only updates the daily automatic run installs, plus a required reboot. Packages on the server’s Other updates, not installed automatically list don’t keep it open or make the fix fail. This card also has Ask AI why. See how automated security updates work.
  • Nginx can be upgraded to the official build: replaces the system NGINX with the official nginx.org build and keeps your site configuration. Sites stay online, and it takes about 10 to 20 minutes per server. See how to upgrade NGINX.

While a fix runs, its row shows Fixing… and the card counts progress, such as “0 of 2 done, 1 in progress”. When xCloud confirms the fix, the row shows Fixed.

If a fix fails, the row says why, such as We could not reach the server or Some updates are still waiting, and offers Retry.

Fix with AI or Ask AI why

The card shows the one that suits the problem. Both open the xCloud AI Assistant, which works within your own team permissions.

While the assistant works on a card, that card shows Working on it in the assistant in place of the AI button. Click it to go back to the chat. The card gets its AI button back when the assistant finishes, when the problem is fixed, if the request could not start, or if you start a new chat.

Button What it does Can it change things? Found on
Fix with AI Checks the problem, then works toward fixing it Yes, only after you confirm each change WordPress updates, vulnerabilities, PHP security patch, a required service down
Ask AI why Reads your site or server and explains the cause Not by itself. It may offer a next step and asks first Fatal errors, failed backups, SSL, low disk, high CPU, disconnected servers, security updates, failed setups

After a fix, the assistant reads the state again and tells you whether the problem is gone. It hands you over to support when the fix needs more than it can do. The AI buttons do not appear on the NGINX upgrade card.

Put a card off, or hide it

You do not have to act on everything today. Each card offers the choices that are safe for that problem.

  • Snooze hides the card for 1 day, 1 week or Until the next version.
  • Ignore moves the card to the Ignored tab for 7 days. It comes back after that if the problem is still there.
  • Skip sets aside one row on a card, such as one site out of three. Click Restore on that row to bring it back.
  • Restore on the Ignored tab brings a card back straight away.

The Snooze choices of 1 day, 1 week and Until the next version on a To-Do card

Click the Ignored tab to see hidden cards such as Backups are failing on 1 site

See what was fixed

Open the Done tab to see what was fixed in the last 30 days. Each line says who did it, such as Fixed by a team member or The AI assistant fixed this. It also lists rows someone skipped and any fix that did not finish.

The Done tab of Your to do listing a fixed server and who fixed it

Team roles and white label

Team members see cards only for the servers and sites they can open, and their role decides which fixes they can run. See team roles and permissions.

Team owners and admins also see a For the whole team checkbox. Tick it before Snooze or Ignore to hide a card for everyone. Only an owner or admin can lift that decision.

White label: on a reseller’s dashboard and for their client teams, the list still works. It leaves out the AI buttons, How to fix and the Docs tab, because those belong to xCloud.

Turn the list off for your team

Team owners and admins can turn the list off and go back to page banners.

Step 1: Open the setting

Go to Settings → Customization and find To-Do List.

The To-Do List card with On and Off options on the Customization page

Step 2: Save your choice

Select Off and click Save Settings. Choose a reason in the Turn off the To-Do list? window, then click Turn off.

Everyone in the team now sees the page banners instead. xCloud keeps tracking problems, so the list is up to date if you switch back to On.

For developers: Public API and MCP

The same list is available to your scripts and AI tools.

  • GET /api/v1/todos lists the open items. It needs the read:servers and read:sites token abilities. Add ?status=pending, ignored or snoozed to filter.
  • POST /api/v1/todos/{key}/actions/{action} runs an action: fix, fix_all, skip, restore_target, snooze, ignore, restore or mark_done. It needs write:servers and write:sites, and allows 30 requests a minute.
  • The optional body takes target (one row), duration (1d, 1w or next_version) and scope (me or team).
  • Security items can’t be skipped or ignored over the API or MCP. These are the PHP security patch, plugin and theme vulnerabilities, modified WordPress files, SSL, security updates and OpenLiteSpeed default certificate items. skip or ignore on one returns 422 with “Security to-dos cannot be skipped or ignored through the API or an AI assistant. Open the dashboard to manage this to-do.” and nothing changes. snooze and fix still work. Skip or ignore these items from the dashboard.
  • Requests are safe to retry: send an Idempotency-Key header and a repeated request never runs twice.
  • The Ask AI buttons exist only in the dashboard. Over the API or MCP, your own agent reads the item and acts on it.
  • The MCP tools are todos_index and todos_actions_run. Fixes made through MCP show in the Done tab as made by the AI assistant.

See the fleet overview guide for how tokens and MCP connections work.

Frequently asked questions

Does the To-Do Center fix anything without asking me?

No. A Fix button shows what will change, any downtime and how long it takes, and nothing runs until you click ‘Fix now’. The AI assistant also asks you before it changes anything.

What is the difference between ‘Fix with AI’ and ‘Ask AI why’?

‘Fix with AI’ works toward fixing the problem and asks you before each change. ‘Ask AI why’ reads your site or server and explains the cause. It changes nothing unless it offers a next step and you approve it.

What happens when I click ‘Ignore’ on a card?

The card moves to the ‘Ignored’ tab for 7 days. After that it comes back if the problem is still there. You can bring it back sooner with ‘Restore’.

Why do I not see ‘Ignore’ on some cards?

Cards for problems that can take your sites down, such as a required service that stopped or a server xCloud cannot reach, can only be snoozed. A PHP security patch can be snoozed for 1 day at most. One exception: if xCloud cannot patch PHP on an Nginx server with Ubuntu 20.04, you can click ‘Skip’ on that server’s row.

Does skipping the modified files card hide the site’s own alert?

No. Skip on the To-Do card hides that row for 7 days. The site’s own modified files alert stays, with its own ‘Ignore’ button. ‘Restore’ on the row brings back only the To-Do row.

Can I turn the To-Do Center off?

Yes. A team owner or admin can open ‘Customization’, set ‘To-Do List’ to ‘Off’ and save. Everyone in the team then sees the page banners again. xCloud keeps tracking problems, so the list is up to date if you turn it back on.

How long does the ‘Done’ tab keep my fixes?

The ‘Done’ tab keeps fixed items and their history for 30 days.

If you run into any issues with the To-Do Center, feel free to reach out to our support team.