Job Reports
Brian Holthouse avatar
Written by Brian Holthouse
Updated over a week ago

Recipe Jobs

When an active recipe processes a trigger event and runs its series of actions, it creates a job. Each job holds a unique trigger event and executes its recipe logic based on that data. For example: running If..Then action based on the availability of the data.

Hive Automate provides details into the execution flow of a job, such as the steps that were executed and the input and output data from every step. Hive Automate also supports re-running jobs in cases whereby an error stops a job from full completion.

Viewing Job Reports

The Jobs report page contains a record of all processed jobs for a recipe. To access the Jobs report page, click a recipe and then the Jobs tab.

Viewing Details for a Specific Job

The Job details page shows the input data and output data of each step in the recipe, allowing you to inspect the job and debug it if needed.

To view details of a specific job, click the job in the Job reports page. This will open the Job details page.

Job Metadata And Statuses

The Job details page includes the following job metadata:



Job ID

The ID of the job.

Job start time

The time the job started.

Recipe version

The version of the recipe the job used.


The status of the job.


The description of the recipe.

Runtime user connection

If the recipe used runtime user connections, the specific connections used by the job will display.


The amount of time the job took to finish.

Tasks used

The total number of tasks the job used.

Rerun #

The rerun number of the job.

Job statuses

Jobs can have the following statuses:




Indicates that the job was processed successfully.
​Note: Jobs may show as Completed but not be processed as you expect. To ensure the recipe is working as expected, take a look at how the job processed steps in the recipe.


Indicates that the job ended because of an error. Errors can generally be attributed to failures in executing actions. For example: An app not being reachable.
When an error is encountered, the job stops and no further steps are executed.


Indicates that the job is still being processed.


Indicates that the job containing long actions was paused when the recipe was stopped.


Rare. Indicates that a recipe has pending jobs, but has been modified in a way such that pending jobs can't finish processing.

Paused jobs

Recipes containing long actions may run for a while, depending on the recipe. When a user stops a recipe, the jobs that are in the processing state are paused. Paused jobs resume when the recipe is restarted.

Job Step Details

To view details about a step in the recipe, click on the step. This will open an expanded view of the step, where you can view its input and output data.

Conditional steps

When conditional actions are expanded, there is a single Output tab. This shows whether the condition evaluated to true or false:

  • If true, nested actions are executed and their details can be viewed

  • If false, nested actions aren't executed and the recipe proceeds to the next possible action. Actions that aren't executed will display as Condition not met and their details can't be viewed.

Repeat steps

Note that when expanding repeat steps, steps made during all iterations won't display.

For example: If a repeat step is set up to process a 10 item list, only the last item in the list will display in the Job details page.

Similarly, when an error occurs within a repeat step, the job details will show only the steps carried out in that particular iteration and not any other iteration before that.

Repeat Jobs

Any job (completed, failed, etc.) can be rerun. Hive Automate stores the data of the trigger event and reruns jobs using this copy of the trigger event.

A rerun of a job will always use the latest version of the recipe. If the recipe has been modified since the job ran, the rerun will use the most recent version.

Did this answer your question?