Robovue
Start free
Menu

UiPath monitoring that notices the job that never started.

Orchestrator sends each job’s start and end to Robovue through a webhook. Your team hears by email, or in Slack on the Team plan, when a job fails or doesn’t run at all, alongside every other platform you use.

Start free See the three steps
UiPath OrchestratorSends each job by webhook

Your UiPath bots this morning

Example
  • Invoice matchingExpected 06:00Didn’t run
  • Supplier statementsFaulted at 07:12Failed
  • Daily cash postingCompleted at 07:40On time
  • Email to your team · 06:05Invoice matching didn’t run at 06:00.
  • Slack on the Team plan, #rpa-alerts · 06:05Invoice matching (UiPath) didn’t run.
An example morning: Orchestrator reports each job, and the 06:00 job that never started reaches your team.

What Robovue watches

Every job event Orchestrator sends becomes a run on the bot’s page, and a schedule on the bot catches the jobs that send nothing.

  • Every job’s outcome. A started job shows as running. Completed is a success, faulted is a failure, and stopped is a failure marked Cancelled.
  • Jobs that don’t happen. Give the bot a schedule and Robovue says “Didn’t run” when its time passes with nothing from Orchestrator.
  • One bot per robot. Each is named after the robot, or its process when the job has none, with an owner, tags and a credential expiry date.
  • The whole event. Orchestrator’s event is kept with the run, so the failure detail is one click from the alert.

Connect it in three steps

No code and nothing to install. Orchestrator builds every request itself.

  1. Open UiPath in Connections

    Start free and your webhook URL and UiPath webhook secret are waiting there.

  2. Add a webhook in Orchestrator

    In the tenant’s webhook settings, add one with that URL and secret, the four job events (started, completed, faulted and stopped), and switch it on.

  3. Run any job

    The UiPath page shows the event arrive, or says exactly why it was turned away. Orchestrator can’t send a test event, so the first job you run is recorded.

ExampleWhat step 3 shows in the app

Before the first job

Nothing has arrived yet.

This step checks again every 30 seconds.

Once a job has reported

Connected. The last run was recorded at 07:40.

What Orchestrator sends

The fields Robovue reads from each event. Every response code and limit is in the app’s reference once you’ve signed up.

POST https://app.robovue.co.uk/ingest/{tenantId}/uipath

Orchestrator calls this itself once you add the webhook subscription. You never build these requests; this is what Robovue does with them.

Headers

X-UiPath-Signature Required

set by Orchestrator

Base64 HMAC-SHA256 of the body, keyed with your UiPath webhook secret. Orchestrator computes it from the secret on the subscription.

Body

Orchestrator’s own webhook event. Robovue reads the fields below and stores the whole event as the run’s payload.

type string Required

The event type. job.started records a Running run; job.completed a Success; job.faulted a Failure; job.stopped a Failure categorised Cancelled. Every other type is acknowledged and ignored.

One of job.started job.completed job.faulted job.stopped

For example job.completed

eventId string, up to 200 characters Required

Orchestrator’s id for the event. Identifies the run when the job carries no key.

timestamp timestamp Required

When Orchestrator sent the event.

job object Sometimes

Required for job events

The job. The bot is Robot.Name, else RobotName, Release.ProcessName, Release.Name, Id or Key (trimmed, up to 200 characters). The start is StartTime or StartedAt, the end EndTime, CompletedAt or EndedAt. Key, JobKey or Id ties a job.started to the event that ends the same job. Timestamps without an offset are read as UTC.

Hear about the next faulted job first.

No card and no sales call. Your webhook is ready the moment you sign up.

Start free See pricing