Spaceflows

Track the execution of your flows

The Spaceflows screen displays all workflows available in the workspace. Each flow appears as a card in a grid format, allowing a quick overview of all configured flows.

At the top of the screen, a search bar and filters help locate specific flows. At the bottom, pagination allows navigation when there are many registered flows.

This screen is focused on tracking executions. To create or edit flow structures, go to Settings > Structure > Spaceflow.

The Spaceflow card

Each card represents a workflow and displays:

• Icon — visually identifies the type of flow.
• Name — the flow title.
• Version — the current version of the flow (e.g., v0.0.1).
• Description — a summary of what the flow does.
• Access arrow — click to open the flow details and executions.

Flow details

The details page centralizes the main information of the flow: name, description, current version, and real-time status. In the top right corner, the Open Editor button takes you to the Spaceflow editor in Settings.

Below the main information, the page is organized into two tabs:

Executions

Lists the history of all flow executions, with the following columns:

• Reference — identifier of the linked execution.
• Status — current processing status.
• Version — which version of the Spaceflow the execution occurred in.
• Started at — start date and time.

Use the search field above the table to locate specific executions or customize visible columns through the display settings menu on the right.

Logs

Displays the technical events of the flow in row format, with the following information:

• Level — event severity (information, warning, error).
• Event — the type of recorded event. Examples: workflow.started (flow started), node.started (step started), node.completed (step completed), edge.traversed (transition between steps), node.error (error in a step).
• Message — additional description of the event, when applicable.
• Node — which step of the flow the event refers to (e.g., "Start", "Demand Analysis", "HTTP Request").
• Duration — processing time of the step (e.g., 160ms), when applicable.
• Date — chronological record of the event.

Spaceflow logs are retained for 90 days and automatically deleted after this period.

Pagination at the bottom allows you to define the number of items per page and navigate between them.

Execution details

When selecting an execution in the list, the system opens the details in a side panel on the right.

On the left side, an information column can be expanded by dragging the divider between the column and the canvas. It displays:

• Reference — execution identifier.
• Status and Version — current status and version used.
• Dates — when the flow started and the last update.

The panel is divided into three tabs: Execution Flow, Details, and Logs.

Execution Flow — Canvas view

The canvas displays the visual design of the flow, using colors to indicate the path taken:

• Green — successfully completed steps.
• Yellow — steps in execution (processing data or waiting for an action from the responsible person, such as completing a task).
• Red — step interrupted due to a technical error.

In the top bar of the canvas, you can track the overall status, total execution time, and the count of processed steps. The Center flow button repositions the diagram to the center of the screen.

Inspecting steps

Each step (node) of the flow can be inspected:

• On hover — a floating window displays the step’s input data.

• On click — opens the full step details:
  • Configuration — action parameters (name, responsible parties, content).
  • Input and Output — received data and processed results, in JSON format.
  • Task/Item — references and paths used to fetch dynamic data.
  • Step logs — event history exclusive to that step.

Details

The details tab displays technical and audit data of the execution:

• Reference — unique execution identifier.
• Version — flow version used.
• Started and Updated — date and time of start and last state change.
• Status — current status (Running, Completed, Error).
• Input (Payload) — data received by the flow at trigger time, in JSON format.

Execution logs

The chronological history of all events triggered during execution. Each row records:

• Event type — flow start, step start/completion, transition between steps, error.
• Step — which step of the flow generated the event.
• Duration — processing time (in milliseconds, when applicable).
• Date and time — chronological record with second-level precision.

Visual indicators accompany each event: a "play" icon for start, a "check" for completion, and a "spinner" for ongoing processes.

Manual flows

Some Spaceflows are configured to be started manually by the user instead of being triggered automatically by an event.

The main visual difference is that, on the details screen of a manual flow, a button to start the flow appears to the right of the Open Editor button, in the top right corner. When clicked, the flow is executed and a new execution is created in the list.

If a flow has an error (indicated in red on the canvas), it cannot be reprocessed directly. It is necessary to fix the flow configuration in the editor and run it again.

Execution tracking works the same way as in automatic flows.