Execution & Monitoring

Once a script is saved, you can execute it in the Qinfinite cloud and monitor the results in real-time.

Running a Script

From the Scripts List

1. Find the script in the Scripts tab.
2. Click the Play icon.
3. If the script has required input variables, a dialog prompts you to fill in values (defaults are pre-populated).
4. Click Execute. The script starts running in the cloud.

What Happens During Execution

EXECUTE

Browser Launches

Managed Chromium instance starts in the cloud

Navigate to URL

Opens the script's target URL

Execute Actions

Replays each action sequentially

Capture Artifacts

Screenshots per step, video of full run

COMPLETE

Synchronous vs Asynchronous Execution

The execute endpoint (POST /webautomation/executions/execute) can run a script in two modes, selected by the isSynchronous request flag.

Mode	isSynchronous	Behavior
Asynchronous (default)	false	The call returns immediately with HTTP 202 and an execution id. You poll or watch the Live Monitor for progress.
Synchronous	true	The call blocks until the run finishes and returns the full execution result in the response body.

Asynchronous response — returned right away so the caller is not blocked:

{ "executionId": "abc123", "status": "started", "message": "...", "timestamp": "..." }

Synchronous response — the connection stays open until the run reaches a terminal state. To keep proxies and load balancers from dropping the idle connection, the server streams a heartbeat (a single space byte) at a fixed interval and sets the X-Accel-Buffering: no header. A 1-hour maximum wait ceiling applies; a run that has not finished by then is stopped.

The terminal synchronous body depends on the outcome:

Outcome	status	Body
Completed	COMPLETED	{ executionId, status, message: "Script execution completed", data: <execution>, timestamp }
Timed out	STOPPED	The run hit the 1-hour ceiling and was stopped.
Failed	FAILED	The run ended in error.

The data field carries the full execution object, including step results and any customOutput produced by verify and scraping actions.

Live Monitor

When an execution starts, the Live Monitor opens automatically, providing real-time visibility:

Feature	Description
Live Screenshots	Screenshot stream updated every 2 seconds showing the current browser state.
Step Status	Each action shows its execution status: pending, running, passed, or failed.
Progress Bar	Overall completion percentage based on actions completed.
Duration	Elapsed time since execution started.
Stop Execution	Abort the running script at any point.
Fullscreen Mode	Expand the live screenshot to full screen for better visibility.

Interactive Execution

Some scripts require user interaction during execution:

Interaction	How It Works
OTP / TOTP	When the script reaches an OTP step, a dialog appears asking you to enter the code. The execution pauses until you submit it.
Authentication Numbers	For auth-number flows, the platform displays the number and waits for your approval before proceeding.

Executions Monitor

The Monitor tab shows all past and current executions:

Column	Description
Script Name	Which script was executed.
Status	Running, Completed, Failed, Stopped, or Queued.
Progress	Percentage of actions completed.
Steps	Completed / Total action count.
Duration	Total execution time.
Trigger	How the execution was started (manual, scheduled, API).
Started	Timestamp of when the execution began.

Execution Status Reference

Status	Meaning
Queued	Waiting for a browser instance to become available.
Running	Currently executing actions in the cloud browser.
Completed	All actions finished successfully.
Failed	One or more actions failed during execution.
Stopped	Execution was manually aborted by the user.

Execution Details

Click any execution to view its detailed results. The detail view has five tabs:

Summary

Overview of the execution:

• Script name, target URL, browser information
• Start time, end time, total duration
• Action counts: total, successful, failed
• Overall status

Steps

Per-action breakdown:

Column	Description
Sequence	Action number in the script.
Action	The action type (click, input, launch, etc.)
Target	Element identifier or URL.
Status	Passed or Failed.
Duration	How long this specific action took.
Screenshot	Link to a screenshot, if this step failed (see note below).

Video

Full video recording of the execution (MP4). The video captures everything that happened in the browser from start to finish.

note

Video processing may take a few minutes after execution completes. The status shows Processing until the video is ready.

Screenshots

Gallery of screenshots captured during the run. Click any screenshot to open it in a lightbox with navigation between steps.

note

Screenshots are only captured for failed steps — a fully successful run typically has none. Use the Video tab for a complete visual record of a successful run.

Report

Raw execution report in JSON format. Includes all step results, timings, and metadata. You can:

• Export the report as a JSON file.
• Copy the report to your clipboard.

Output from verification and web scraping actions appears here under customOutput, keyed by each action's capture-variable name. The same data is available from the execution's result view.

Troubleshooting Executions

Problem	Possible Cause	Solution
Script fails on first action	Target URL is unreachable from the cloud	Verify the URL is accessible and not behind a firewall.
Element not found	Selector changed since recording	Edit the script and update the identifier. Use stable selectors (ID, name, aria-label).
Timeout on action	Page loads slowly in cloud environment	Increase the action timeout or add a wait step before the action.
OTP dialog not appearing	Action not tagged as OTP type	Edit the action and set it to setotp type.
Video not available	Processing still in progress	Wait a few minutes and refresh.

Next Steps

• Script Management — Edit scripts to fix issues found during execution
• Recording Guide — Record a new version of the script
• Web Recorder Extension — Learn about extension features