Execution & Trust

MIFY classifies every workflow execution by how much you can trust its reproducibility.

Execution Classes

Every node belongs to one of three classes:

Class	Behavior	Examples
Deterministic	Same input always produces same output	Template, JavaScript, Route If
Probabilistic	Output may vary (AI models)	Chat, Embed, Image Generate
Opaque	External platform execution (black box)	Dify App, Flowise Flow

Trust Levels

Trust level is determined by the “least trusted” node in your workflow:

Trust Level	When	Guarantees
Trusted	All nodes are deterministic	Full caching, safe replay, authoritative comparisons
Semi-Trusted	Contains probabilistic (AI) nodes	Partial caching, replay with warnings
Opaque	Contains external platform nodes	No caching, unsafe replay

Rigor Modes

Mode	Use Case	What It Does
Experimental (default)	Development, iteration	Minimal overhead, fast execution
Audited	Compliance, regulated workflows	Full audit trail, integrity hashing, immutable logs

Execution Lifecycle

Every workflow run progresses through these states:

pending → running → completed
                  → failed
                  → cancelled
          waiting (paused for HITL)

Comparison & Replay

• Baselines: Set a reference execution to compare against
• Side-by-side comparison: Diff two runs to see what changed
• Replay: Re-run a workflow with the same inputs (deterministic nodes produce identical results)

Batch Processing

Run workflows at scale:

• Submit batches with configurable concurrency
• Pause, resume, or cancel batches
• Stop-on-error to halt on first failure
• Progress tracking per batch item