Runs and logs
Start an execution
Open a pipeline and select Run. Codinamo creates a run with a canonical RUN-… identifier, publishes its request to the execution engine, and displays the run page. The workspace-level Runs menu lists runs across its pipelines.
Read the result
- Run status
-
The overall lifecycle, from queued to a terminal result.
- Action progress
-
The current state of each user-facing action.
- Logs
-
Runtime messages and ordered output emitted by actions.
- Outputs
-
Values exported into the execution context and recorded in logs.
- Test reports
-
Aggregated JUnit counts and duration emitted by
TEST_REPORT.
Exact occurrences of secrets attached to the pipeline are replaced with three asterisks before logs are persisted. This protection does not cover values transformed by an action, so actions must still avoid printing credentials.
Stop an execution
An active execution can receive a cancellation request. The request is asynchronous: the status may temporarily show that cancellation has been requested while the execution engine reaches a safe stopping point.
Continue on error
When disabled, an action failure prevents dependent actions from proceeding and the execution fails. When enabled, Codinamo records the failed action, allows eligible downstream work to continue, and can finish with a partial-success result.
See Execution statuses.