History & Audit

Every bot run is logged with its status, duration, version, asset environment, output log, and an estimated time saved. The Audit Trail records workspace-level actions such as publishing bots, changing credentials, and inviting members.

Execution History

Go to Web Console → History to see all executions in your workspace. Each row shows:

Bot name and version number (v3 badge)
Start time and duration
Exit status — Success, Failed, Cancelled
Asset environment used (Dev / Staging / Prod)
Time saved estimate
Runner that executed the job

Click any row to expand the full output log — the captured stdout and stderr from the Python process, including any print statements in the bot script.

Status badges

v3

The bot was dispatched at version 3. Click to compare with the current version.

Hash OK

The imported bot's script hash matched the last verified snapshot before running.

Hash Mismatch

The script file was modified since the last Re-sync. The bot still ran (unless Strict Mode is enabled).

Dev / Staging / Prod

Which asset environment was used for credential resolution in this run.

Note — History shows executions dispatched by Runners. Jobs that never reached a Runner (e.g., rejected because of an incompatible OS or a BLOCK_RUN flag) appear as failed queue executions in the Queues view, not in History.

Controlling Active Jobs

While a bot is running, its card on the Bots page shows live controls:

⏸ Pause

Sends a pause signal to the Runner. The Python process is frozen in memory (zero CPU) and can be resumed at any time.

▶ Resume

Unfreezes the Python process. Execution continues exactly where it was paused — no data loss, no restart.

⏹ Stop

Terminates the bot immediately. The job is marked as Cancelled and the log is flushed with whatever was captured up to that point.

Time Saved / ROI

KlangoRPA tracks time saved per execution automatically — no manual input required. The estimate is based on the actions the bot performed and how long those actions would typically take a human.

How it works:

The generated Python script includes inline counters that increment as each action completes — one tally per action type (click, type, navigate, extract, etc.).
When the bot finishes, the Runner sends the tally to the Management server along with the result.
The server multiplies tally counts by pre-configured seconds-per-action weights to produce timeSavedSeconds for that run.
The History view and the Dashboard's Time Savedcard aggregate these values over the selected period.

Override per bot

If the automatic estimate doesn't match reality, you can set a manual override in Bot Config → Time Spent per Execution (in minutes). This value multiplies by the number of loop iterations the bot performed, so it scales correctly for data-driven bots.

Dashboard card

The Home page shows a Time Saved card that sums all executions in the selected date range. The value is shown in hours or minutes and updates instantly when you change the period filter.

Audit Trail

The Audit Trail records workspace-level events — actions taken by admins and members that affect the workspace configuration.

What's logged:

Bot created, updated, published, or deleted
Asset created, updated, or deleted
Runner created, deleted, or API key regenerated
Trigger created, updated, or deleted
Queue created, updated, or deleted
Member invited, role changed, or removed
Workspace preferences changed (LLM keys, SMTP, storage)
Library approved or rejected

Access the Audit Trail at Web Console → Audit. Each entry shows the timestamp, acting user, event type, and affected resource.

Note — Audit Trail is available to users with the Admin role or above. Members with lower roles cannot see who changed what — they only see their own executions in History.

Workspace Roles & Permissions

KlangoRPA uses hierarchical roles to control who can read, run, and modify automations in a workspace:

Role	Permissions
Monitor	View bots, history, and audit trail. Cannot run bots or modify anything.
Runner	Same as Monitor, plus can manually dispatch bots.
Dev	Can create and edit bots, assets, triggers, queues, and workflows. Cannot manage members or approve libraries.
Admin	All Dev permissions, plus manage members, approve library packages, and view the full audit trail.
Owner	Full control. Can transfer or delete the workspace.

Manage workspace members at Web Console → Workspace → Members. Invite teammates by email — they receive a link to register (or log in if they already have an account) and are added to your workspace automatically.