Reviewing the Activity Log

When you start a task in the console (for example, deploying a database or restoring from a backup), the console adds the task to the table on the Activity Log page. The Activity Log organizes console activity into a table that you can sort and filter.

The Activity Log page displays the following columns:

• Task name identifies the type of task for the table entry (for example, create-managed, restore-managed, or update-managed-size). The console displays the raw name the API gives the task, with a tooltip that names the task in plain language and explains what it does.

• Subject kind is the kind of resource the task acted on, one of database, cluster, or ingress.

• Subject ID is the ID of that resource. For a Managed database, this is the database ID displayed in the Details pane.
• Status indicates the state of the task. The values are running, succeeded, queued, and failed.
• Created at is the timestamp at which the task started.
• Updated at is the timestamp at which the console last updated the task.

Use the arrow to the left of a Task name to expand the task information and view the task's own steps and their progress.

Filtering and Sorting the Activity Log

The Activity Log table supports filtering and sorting by column value. A drop-down filter icon located next to each column name lists the available values for that column. Select a value from the filter drop-down to restrict the table to matching rows. Select the arrow between the column name and the filter drop-down to reverse the display order based on that column.

Managed Task Names

Every Managed operation writes a task. The following table describes the task names currently in use:

Some task names are easy to misread against what actually happened in the console:

• update-managed cannot tell you which service changed. Every services write shares this task type. To find out what changed, expand the row and read the steps, or review the AI Services pane.
• update-managed-size refers to a resize, not a generic update. This is the task associated with the Upgrade size action described in Accessing Management Options with the Actions Menu.

What Succeeded Does Not Tell You

A task that reads succeeded means the operation itself finished, and the console has already applied the resulting status change; there is no lag between the two. The task record itself does not say which status resulted, or whether the database is usable.

Delete is an exception to this behavior: a successful delete removes the database record, so its disappearance from the list confirms success. If a delete leaves the database behind, the task failed.

A services change is the other exception: a succeeded update-managed means the API has finished its side of the change, but the deployed server itself takes longer to reflect it. Expect roughly a minute or two for a configure, and fifteen to twenty seconds for a first MCP enable.