---
title: Managing and Monitoring Workflows
description: Enable effective monitoring and proactive management of data workflows—track performance, detect issues, and maintain streamlined operations across pipelines.
---

import { Aside, Steps } from "@astrojs/starlight/components";

Once workflows in Infoveave are scheduled or triggered through mechanisms like manual triggers, webhooks, or email triggers, the next is to monitor and manage their execution. Infoveave provides the Workflow Execution Status feature to track the progress of workflows, identify issues, and ensure that they perform as expected. 

## What is Workflow Execution Status?

The Workflow Execution Status feature allows you to monitor workflows in real time. It shows you how a workflow is progressing, whether it has succeeded, is still running, or has failed. You can see detailed information about each task, including when it started, how long it took, and how much data it processed.

<Aside type="note" title="Example">
If a workflow is scheduled to process transaction data for **ABC Bank** every day at **6:00 AM**, Workflow Execution Status will show whether the workflow completed successfully. 
</Aside>

## Key Features of Workflow Execution Status

- **Real-Time Monitoring:** The real-time monitoring feature shows the status of a workflow while it runs. You can see which tasks are complete, which ones are in progress, and which ones are pending. It also displays execution times for each step and the amount of data being processed.

<Aside type="note" title="Example">
If a webhook triggers a workflow to process a new file uploaded by Symmonds Agency, real-time monitoring will show:

- The file upload step.

- Data transformations, such as concatenating fields.

- The final output generation step.
</Aside>

- **Instance History:** Infoveave keeps a record of all workflow runs through the **Instance History**. This history includes the start and end times of workflows, their duration, and their success or failure. You can filter this information to focus on specific runs based on dates or statuses.

<Aside type="note" title="Example">
If a daily workflow processes ABC Bank’s loan data, the instance history will confirm that it ran at 6:00 AM, took 3 minutes to complete, and successfully processed all the required rows. If the workflow fails, the history will log the error, so you can troubleshoot and rerun it. It highlights:

- **Start and End Times:** When the workflow ran and how long it took.

- **Execution Status:** Whether it succeeded or failed.

- **Logs:** Detailed logs of each task, including data processed and any errors encountered
</Aside>

- **Error Reporting:** If a workflow fails, Infoveave provides detailed error messages to help you identify and fix the problem quickly. It highlights the specific step where the failure occurred and explains the reason.

<Aside type="note" title="Example">
If an email-triggered workflow processing branch data from PVR Consultancy fails because a Loan ID is missing, Workflow Execution Status will pinpoint the issue. You can fix the input data and rerun the workflow from the failed step instead of starting over. This saves time and ensures the workflow completes successfully.
</Aside>

- **Workflow Controls:** Infoveave provides the option to control workflows during execution.
    
    - **Pause and Resume:** If something unexpected happens, you can pause a workflow and resume it after resolving the issue. 

<Aside type="note" title="Example">
If an uploaded file is incomplete, you can pause the workflow, replace the file, and then resume.
</Aside>

    - **Rerun Workflows:** If a workflow fails, you can rerun it either from the beginning or from the specific task that caused the failure. 

<Aside type="note" title="Example">
If a transformation step in the workflow fails, you can correct the data and rerun only that step instead of redoing the entire process.
</Aside>