Skip to main content
Flowker helps compliance teams answer two questions: was the transaction validated before it reached the ledger, and what did each step of that validation do?

​
Validation before the ledger

Flowker runs a workflow’s nodes in the order its graph defines, and it has no join node that waits for parallel branches to converge. Chain your validation nodes in sequence ahead of the node that writes to the ledger, and:
  • The ledger write runs only after every preceding check returns a result
  • A conditional node on the verdict stops the flow before the write when a check fails
  • You do not depend on post-write validation and the corrections it forces
  • The execution record shows the sequence: the checks that ran, their verdicts, then the write
This is a preventive design. You place the checks ahead of the write, and Flowker holds that order for every execution.

​
Execution records

Each workflow execution keeps a step-level record of what ran. For every step, the record holds the step name and number, when it ran, its status, how long it took, the output it returned, and the error message if it failed.
  • Use List executions to find executions. Filter by workflow and by status, then page through the results with a cursor.
  • Use Get execution results to read the step detail of one execution.
The same record is available in Lerian Console on the Executions page.

​
What’s next

Security

Learn about Flowker’s authentication model, encryption, and resilience features.

Executions API

Query execution history and step-level results through the API.