Skip to content

Site activity

Every action CloudPress performs on a site — a plugin install, a backup, a cache purge, a restart, a package change — is recorded as a task. The Activity page is the site's history of those tasks: what was done, whether it succeeded, who asked for it, and when it finished.

It is a read-only record. Nothing on the page starts, retries, or cancels work.

Before you start

  • A site that has finished provisioning, so its site pages are reachable.
  • Membership of the workspace that owns the site. Activity is a view-level page — anyone who can open the site can read it, with no edit, billing, or admin role required.

Open the Activity page

  1. Open the site from My Sites in the workspace sidebar.
  2. In the site's left sidebar, open the Analytics & Logs menu.
  3. Choose Activity. The page is titled Activity, with the site's name above it.

If the site has no recorded tasks yet, the table shows "No activity recorded for this site yet".

What the table shows

Entries are listed newest first. Each row is one task.

Column What it shows
Status The task's current state, shown as a coloured dot and a status word: PENDING, RUNNING, PAUSED, CANCELLED, OK, or FAILED. These render as-is and stay in English. A RUNNING task's dot animates.
Action The kind of task, in plain language — for example Install Plugin, Create Backup, Change PHP Version, Restart Site, or Purge Cache.
Message The task's own description, set when the task was created.
Performed by Who the action is attributed to — see below.
Completed On When the task finished, in your browser's local time. A task that is still pending, running, or paused shows a spinner here instead of a time.

OK means finished successfully

The status words come straight from the task record. OK is the success state; FAILED is the one to investigate, and PAUSED means the task is waiting on something external before it can continue.

Who "Performed by" names

Not every task is started by a person in your workspace. Some are started by the platform itself, and some by support staff acting on a ticket. Internal identities are never shown to customers, so the column resolves to one of three things:

  • A teammate's name — shown as their first name and last initial, for tasks a user in your own workspace performed.
  • System — for tasks the platform started on its own, such as work initiated by the hosting infrastructure rather than by a person.
  • Support — for tasks performed by CloudPress staff.

The same masking applies over the API, which reports System and Support with a null id and email in place of the real account. See Tasks.

How much history you get

The page is not time-limited: it lists the site's tasks from the beginning of its history, not just a recent window. It is paginated instead — 25 entries per page, with paging controls at the bottom of the card once there is more than one page.

There is no filter, search box, or date picker on this page. To narrow the list by status, or to pull only today's entries, use the API (below).

Activity is not the Log Viewer

These two pages answer different questions, and it is worth keeping them apart:

Activity Log Viewer
Records Actions CloudPress took on the site — the control-plane history Traffic and errors from the running site — the request-level record
Typical row An action such as "Install Plugin", with its status and who ran it An HTTP request, or a web-server error line
Answers Did that restart go through? Who changed the PHP version? Why is this page returning a 500? Where is this traffic coming from?

Shield's Security Events page is a third, separate record — what Shield blocked or challenged. For both of those, see Viewing logs.

Over the API

The same task history is available as JSON, most recent first:

curl -H "Authorization: Bearer $CLOUDPRESS_TOKEN" -H "X-Auth-Account: $ACCOUNT_ID" \
  "https://my.cloudpress.com/api/sites/$SITE_ID/tasks"

The API differs from the dashboard in three useful ways:

  • It filters. The filter is a path segment rather than a query parameter — request https://my.cloudpress.com/api/sites/$SITE_ID/tasks/OK/filter for one of OK, PENDING, RUNNING, CANCELLED, PAUSED and FAILED, or TODAY for everything from today.
  • It returns more per task, including the raw output the dashboard doesn't print, the task's internal name, and both start and end timestamps.
  • It caps rather than pages. Any response returns at most the 100 most recent tasks, where the dashboard pages through the full history.

Full field list and error codes: Tasks.

Next steps