Workflows

A workflow is a chain of functions that work together as one longer process — for example, "take the order, charge the card, then arrange shipping." This view is about watching those workflows actually run in production: which ones are running now, how each one went, and what happened at every step.

Annotated screenshot of the deployed Workflows panel showing a list of workflow runs with status (Running, Completed, Failed) and durations, one expanded to show step-by-step run history, callout: "Watch long-running jobs as they execute and review every past run."

Watching a workflow run

Each time a workflow runs, that run is recorded as its own entry you can open up.

• Live executions. See what's running right now and how far along it is.
• Run history. Every past run is kept, with its status — for example Running, Completed, or Failed — and how long it took.
• Step by step. Open any run to see each step in order, so if something failed at step 3, you can see exactly where and why.

Did it finish, or fail partway?

You never have to wonder. Every run shows its outcome plainly. A workflow that completed shows as done; one that stopped partway is clearly marked as failed, with the failing step visible so you can understand what went wrong.

Who does a workflow act as?

This matters for trust and accountability, so Pikku Studio Cloud is strict about it: a workflow runs as the person who triggered it. That identity flows through every step of the chain — the workflow can only do what that person is allowed to do. And every action is recorded in the audit log, so you can always see who did what.

A workflow can't quietly act as someone it shouldn't. It runs with the identity of whoever triggered it, that identity carries through every step, and the audit log records it all. See Credentials.

Design-time vs run-time

This page is the running view — workflows live in production. If instead you want to inspect how a workflow is built — its steps and shape before it runs — that's the design-time view in the Builder. See Building workflows.

Where to go next

• Building workflows — inspect a workflow's design before it runs.
• Credentials — how identity flows through a run and into the audit log.
• Async — schedulers, queues, and triggers that can start a workflow.