Docs / Start here / The platform / Activity
Activity
Activity is the record of what your workflows did. Overview sums up runs, cost and estimated value, Runs lists each run, and Events lists each event.
Activity has three tabs. Overview turns the runs of your workflows into figures for a period. Runs lists every recorded run, and Events lists the events OAIZ has stored. Each tab covers the workflows and events you have access to.
Overview
Overview shows how many times your workflows ran, how often they succeeded, what they cost and, once you describe what a run is worth, the value they delivered. The period picker offers Last 7 days, Last 30 days, Last 90 days, This month, Last month and This year, or any range of up to 366 days on its calendar. Last 30 days is the default.
All folders narrows every figure to one Library folder and the folders inside it. It appears once your workflows sit in more than one folder. Analytics on a Library folder opens Overview for that folder. Amounts are in your organization’s billing currency.
- Runs
- Production runs in the period, with how many succeeded and failed.
- Running cost
- What OAIZ billed for the AI, tools and compute the workflows used in the period. Unlike the run figures, it includes failed runs and test runs.
- Success rate
- The share of production runs that succeeded, to one decimal place. When runs failed, the panel names the workflows with the most failures, and its failed count opens Runs filtered to the Failed status.
- Time saved
- The minutes of manual work replaced by qualifying runs. It appears once a workflow has a Time saved value model.
- Labour value
- The estimated value of qualifying runs, from each workflow’s value model.
- Net value
- Labour value minus the running cost of the workflows that have a value model.
- ROI
- Net value as a percentage of the running cost of the workflows that have a value model. It sits above the Value and running cost chart and is missing while that running cost is zero.
The success calendar beside the rate always covers the last 12 months, whatever the period. Each day is marked 100%, 90 to 99% or Under 90%. Selecting a day with failures opens Runs filtered to that day’s failed runs.
Below the figures, the Value and running cost chart plots both amounts across the period. Until a workflow has a value model, it is Running cost over time. Running cost by workflow ranks the workflows that cost the most, and each bar opens that workflow’s Analytics tab. Runs per day shows the production runs on each day.
The Workflows table lists every workflow in scope with its Runs, Success rate and Running cost. Time saved, Labour value, Net value and Value model join them once any workflow has a value model. Search workflows matches a workflow or folder name, and the value model filter shows All value models, Configured, Time saved, Direct monetary value or Not configured. View opens a workflow’s Analytics tab. A workflow without a value model shows Configure instead when you can change it.
Estimated value
Value is an estimate built from assumptions you set for each workflow, called a value model. OAIZ multiplies them by recorded runs and does not measure the outcome itself. Configure value sets the model. It appears in the Workflows table and on the workflow’s Analytics tab for people who can change the workflow.
- Time saved
- Manual work is the minutes of work one successful run replaces, and Hourly labour cost is what that work costs per hour. Each qualifying run is worth the minutes divided by 60, times the hourly cost.
- Direct monetary value
- A fixed amount each qualifying run is worth, such as the fee for one processed order.
A qualifying run is a successful production run. Failed runs and test runs earn no value. Each run uses the assumptions that were active when it completed, so changing them does not rewrite earlier runs.
Apply from sets the date the assumptions start. For a first value model, an earlier date gives past runs a value. Later, keeping the date corrects the current assumptions, and a later date starts new ones while earlier runs keep the old ones. A date before the latest start is refused. Basis for this estimate is an optional note of up to 1,000 characters.
Workflows with a value model shows how many workflows in scope have one. Labour value, Net value and ROI leave out the others entirely, including their running cost. Its Configure button, such as Configure 3 workflows, filters the table to the workflows without a value model that you can change.
Analytics for one workflow
The Analytics tab in a workflow shows the same figures for that workflow alone, with its own period picker. It adds How value is calculated, which shows the qualifying runs and the formula behind the estimate, and Recent runs, which lists its latest production runs.
Runs
Runs lists the recorded runs of the workflows you can open, test runs included. It can therefore show runs that Overview leaves out. What a run is and what each status means are explained on the Runs page.
Each row shows the run’s status, its workflow and a Re-run badge when it replays an earlier run. Deleted marks a run whose workflow has since been deleted. Date, Started, Duration and Cost can be shown or hidden with Columns, and each sorts the list.
Select workflow narrows the list to one workflow. More filters holds Statuses and Date range, and Clear all removes every filter. The filters are kept in the page address, so a copied address opens the same view. With Live Feed on, new runs appear as they arrive. With it off, the list holds still and Refresh reloads it.
Opening a run shows it inside the tab. Back to runs returns to the list, Previous run and Next run move through the loaded runs, and Copy run link copies an address that opens this run with the current filters. A run opened from a link that falls outside the filters still opens, with a notice. The Logs page explains how to read the run itself.
Events
Events lists the stored events you can read. The Events page explains what an event contains and where events come from.
Each row shows the Integration that produced the event, or Oaiz when no integration did, with its Event type, Created at and Attachments. Event ID is hidden until you add it with Columns. Selecting a row’s event type shows only events of that type.
Search matches the event ID, event type, user identifier, and property names and values. Select event type picks one type. More filters holds Date range and Integrations. Live Feed works as it does on Runs.
A row’s menu has Open, Open in new tab, Add to chat, Show only this event type and Copy event ID. Add to chat attaches the event to your next Chat message as context. Selecting several rows offers Add to chat for all of them.
Opening an event shows its Type, Created time, UUID, User, User UUID and Aggregation. Attachments holds its stored files, and Attachments not kept lists files that arrived with it but were not stored. Event properties shows the content as JSON. Triggered runs lists the runs the event started, with their workflow, status and start time, and Open log opens a run in Log Details.
Publish an event from the app
Add Custom Event opens a sheet that publishes one event. Under Event type, a Provider and a Name form the event identifier, such as e:custom/order-completed. Add Property adds a key with a String, Number, Boolean, Object or Array value.
Optional Fields holds Timestamp, set to the current time, User Identifier, set to your email address, Namespace ID, User Aggregation ID and Unique Key. Timestamp and Unique Key work as described for events sent through the API.
Publish Event sends the event the same way as the ingest API. Any live workflow that listens for its type starts.
Edit as New Event, on a row or on an event’s page, opens the same sheet filled with that event’s type, properties and identifiers. Timestamp is reset to the current time, Unique Key is empty and attachments are not copied. Publishing creates a separate event and leaves the original unchanged.