Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mantrixflow.com/llms.txt

Use this file to discover all available pages before exploring further.

Run history is where operational truth lives. There are two places to review it:
  • Builder history panel — click the clock/history icon in the builder top bar to see runs for the current pipeline
  • Activity Log (/workspace/activity) — org-wide view of all events across all pipelines, connections, and data sources

​
What to look for after every important change

  • run status
  • start and end time
  • row counts or records processed
  • error messages
  • whether the run happened manually or from a schedule

​
Healthy first-run checklist

A healthy first production run usually looks like this:
  1. source and destination connections both test successfully
  2. pipeline saves without validation errors
  3. manual run completes
  4. destination contains the expected table updates
  5. only after that does the team enable the schedule

​
Sync state in run operations

Incremental pipelines keep state between runs so MantrixFlow knows where to resume. That state is why later incremental runs are faster and more targeted than the first one.

​
Activity Log

The Activity Log page (/workspace/activity) shows all workspace events with:
  • Summary badges — Total, Success, Failed, Created, Updated, Deleted counts
  • Filter bar — free-text search plus dropdowns for All Types, All Actions, All Status, and time window (Last 7 days, etc.)
  • Table columns — Timestamp, Entity Type (Pipeline, Pipeline_run, Data_source, Data_source_connection), Action Type, Message, Status, Metadata
Entity types you will commonly see:
Entity typeWhen you see it
Pipelinepipeline created or updated
Pipeline_runrun started, completed, or promoted
Data_sourceschema discovered
Data_source_connectionconnection tested

​
When to investigate immediately

Investigate right away if you see:
  • a run that fails immediately after a credential rotation
  • row counts unexpectedly dropping to zero
  • repeated errors on the same destination node
  • a scheduled run that produces no destination changes

​
Good operator habit

When a run fails, check the builder history icon for the specific pipeline error and the Activity Log for the full event trace. The Activity Log is especially useful when multiple pipelines are affected.