Skip to content

Virtual Run Preview

Virtual Run is GloriaMundo’s “glass box” preview: it shows you what a workflow will do before it makes real-world changes. You’ll see step-by-step results, previews of content that would be posted or sent, and warnings for actions that create, modify, or delete data.


The Glass Box Principle in Action

GloriaMundo is built around a simple promise: you can review before you commit.

Virtual Run helps you:

  • Validate the workflow’s logic and data flow
  • Confirm destinations (the right channel, folder, spreadsheet, list, etc.)
  • Review generated text and media before anything goes live
  • Catch missing connections or unbound resources early
  • Understand expected cost before running

What You See in a Virtual Run

Step-by-Step Outcomes

Virtual Run shows each step with a clear outcome (success, warning, skipped, or failed) and the relevant inputs and outputs. This makes it easier to debug workflows without guessing what happened.

Some steps can safely run during preview to produce realistic intermediate data. Steps that would write to external systems are previewed instead of executed, so you can see the effect without committing it.

Previews Of External Writes

For steps that send, post, create, update, or delete, Virtual Run shows a “what will happen” preview. For example: the exact message text, the draft post content, or a summary of the record that would be created.

This is especially useful for content workflows (emails, social posts, announcements) where you want to verify tone and formatting before publishing.


Warnings For High-Impact Actions

Virtual Run flags steps that are likely to be sensitive, including actions that:

  • Create or modify external data
  • Send outbound communications
  • Delete records or files
  • Perform irreversible actions

You can use these warnings to decide whether to:

  • Adjust the workflow (add a review step, add a filter, change a destination)
  • Run in a safer mode that requires stronger confirmation
  • Keep the workflow disabled until it’s ready

See Running Workflows for execution modes and confirmations.


Cost Preview

Virtual Run provides an estimate of what a live run is expected to consume, so you can decide whether to proceed before executing. This is useful for workflows that fan out across many steps, generate a lot of content, or call multiple connected services.

Connection Checks And “Connected As”

If a workflow requires a connected service, Virtual Run will surface missing connections and show which identity is connected for relevant steps (when available). This helps avoid “it posted to the wrong account” surprises.

See Connecting Services.

Resource Binding (Pick The Exact Channel, File, Sheet, Etc.)

Many workflows need a specific resource inside a service: the exact Slack channel, the correct spreadsheet, the right Notion database, and so on. Virtual Run can prompt you to select these resources and can suggest likely choices to speed setup.

Until resources are bound, the workflow may be blocked from executing “for real” to prevent unintended writes.

Downloadable Preview Reports

You can download a Virtual Run report (for example, as Markdown or JSON) for review, sharing, or record-keeping.

Simulation History

Virtual Run keeps a history of previews for a workflow so you can revisit what was reviewed and compare changes over time. This is useful when you’re iterating on a workflow, onboarding teammates, or troubleshooting why a live run behaved differently than expected.

“Run For Real” After Preview

After a successful Virtual Run (and once connections/resources are ready), you can proceed to run the workflow live from the same interface. This helps turn preview into a real operational safety step, not just a one-off simulation.

For higher-stakes workflows, enable Safe mode and require Virtual Run before executing live. See Governance & Safety.

Summary

Virtual Run is your safety net. Before any workflow touches the real world:

  1. You see the workflow step-by-step
  2. You review external effects before they happen
  3. You bind connections and resources intentionally
  4. You preview expected cost
  5. You choose whether to run live

No surprises. No accidents. Full transparency. That's the Glass Box principle.