Skip to content
ricochet

Processes

Open Processes in the sidebar to see every app worker and task invocation running on your items, with the memory and CPU each one uses. The page is available to users with the Developer or Admin role.

It lists processes of items you own or collaborate on with the Contributor role or higher. Select an item’s name to open its runtime tab.

The Processes page listing three app workers and two task invocations, each with its running time, connections, memory, peak memory, CPU in cores with any limit, and a Stop button
The Processes page listing three app workers and two task invocations, each with its running time, connections, memory, peak memory, CPU in cores with any limit, and a Stop button
ColumnMeaning
Running forHow long the process has run, with its start time in UTC
ConnectionsOpen connections to an app worker, shown as - for task invocations
MemoryMemory the process uses now
PeakThe most memory the process has used since it started
CPUCPU cores in use, beside the item’s CPU limit when one applies

The CPU limit is the one set in the item’s runtime settings. It shows only on servers that run content in Docker or Kubernetes, since other servers do not limit CPU.

  • Type in Search to match item names.
  • Open the filter menu to show only app workers, only task invocations, or chosen content types.
  • Select a column header to sort by it, and select it again to reverse the order.

The list refreshes every 30 seconds. Pick another interval from Refresh, from 5 seconds to 5 minutes. The page returns to 30 seconds the next time you open it.

Select Stop on a row and confirm.

  • Stopping an app worker ends the session of anyone connected to it. The app starts a new worker when it next needs one.
  • Stopping a task invocation ends that invocation only. The task’s schedule stays in place.

Admins can switch between My items and All items to see every process on the server, and can stop any of them.