PrompteryxBeta
    ⌘K
    PlatformSupport
    Menu
    IntroductionInstall Desktop & extensionQuick StartPlatform Overview
    OverviewWhat you can makeAI Browser Agent in the chatModels and AutoConnectorsSchedulesProjectsExplore and publishingShare linksMemory and SkillsPersonal agent (beta)Welcome, settings and skinsPlans, credits and top-upsPrompteryx DesktopGroups (pilot)Phone app (early access)
    OverviewCreating WorkflowsTesting & DebuggingScheduling
    OverviewGetting StartedCommandsRecordingSettingsStructured OutputParallel AgentsTips & Best Practices
    OverviewInstallationSidebar AgentUsing Attached FilesExecute on Current TabExporting to Visual Studio
    Overview
    OverviewOpen PageClickClick CoordinatesFillExtract TextScreenshotWaitPress KeyFocus ElementBlur ElementSelect TextHighlight ElementSet ViewportGet Bounding BoxScrollHoverSelect OptionAssertionsCookiesEvaluate JavaScriptExample Workflows
    OverviewPrompteryx Browser AgentOpenAI
    OverviewSchedule TriggerWebhook Trigger
    OverviewGoogle SheetsGoogle CalendarConnect Hub (3,000+ apps)Example Workflows
    AI Vision SettingsChrome Automation ProfilesCloud BrowserBrowser Profiles & Persistent ContextVideo RecordingExecution LogsSharing & CollaborationEdit History
    Selectors GuideVariables
    Start hereGet an API keyRun the AI browser agentDrive a cloud browserRun workflows from anywhereUse connected apps (Connect Hub)SDK (TypeScript)CLIMCP for AI assistants
    REST APIWebhooksMCP toolsCloud Browser APICloud Browser quickstartMigrate from Browserbasen8nZapierMake.com

    Need help? Contact Support

    1. Documentation
    3. Features
    5. Execution Logs

    Execution Logs

    Feature

    Monitor and debug workflow execution in real-time

    Overview

    Execution logs provide real-time visibility into what your workflow is doing. Each action is logged with a status, and every node's input and output data is kept for you to inspect.

    Viewing Logs

    The Execution Results panel at the bottom of Visual Studio opens when a run starts (toggle it with Log in the header). It shows:

    • Real-time logs - Watch each step as it executes, starting with the run's settings (profile, video recording, visibility)
    • Status indicators - Each node in the Nodes column shows whether it succeeded, failed, was skipped or is still waiting
    • Execution time - How long each node took
    • Output data - Values extracted or returned by each node

    Path Filter

    Filtering Parallel Branches

    For workflows with parallel execution (Parallel Split/Join nodes), use the path filter to focus on specific branches:

    • All Paths - Show all logs from all branches
    • Main - Show logs before split and after convergence
    • Branch-1, Branch-2, etc. - Show logs from specific branches
    The path filter appears automatically when your workflow has parallel branches.

    Log Details

    Node Output
    Select a node in the Nodes column to see its Input and Output (as a table, JSON or schema). Depending on the node, this includes:
    • Extracted data (text, attributes, etc.)
    • Page URL at execution time
    • Selector used
    • Execution duration
    Error Details
    When a node fails:
    • The error is shown in red in the logs
    • The failed node is marked in the Nodes column
    • Selecting it shows the error message alongside its input

    Execution History

    Visual Studio's History view: the Executions list on the left with auto-refresh, and the execution detail pane on the right
    The Editor / History toggle in the Visual Studio toolbar switches to the Executions view — every run's status, logs and outputs live here.

    All workflow executions are saved in the execution history. Access it from:

    • Visual Studio → History (the Editor / History toggle in the header)
    • Dashboard → Execution History (/dashboard)

    Each entry shows: start time, status (Succeeded, Failed, Running or Stopped by user), duration, and who ran it. Click it to view the run's logs and each node's results, and Watch Recording if the run was recorded.

    Best Practices

    Use Descriptive Node Names
    Rename your nodes to describe what they do (e.g., "Fill Email Field" instead of "Fill 1"). This makes logs much easier to understand.
    Add Screenshot Checkpoints
    Add Screenshot nodes at key points in your workflow. When reviewing logs, you can see the page state at important moments.

    Related Documentation

    Video Recording

    Visual execution capture

    Testing Workflows

    Debugging techniques