Skip to main content

Troubleshooting Flow Executions in Integration Hub

Overview

The Integration Hub centralizes all Fenergo SaaS integration services - Event Ingress, Integration Flows, and Event Notifications—allowing technical users to monitor, diagnose, and troubleshoot integration issues from a single location.
​Integration Hub
​

This article explains how to troubleshoot failures in Flow Executions, how to interpret Step Logs, and how to use the General Logs tab.

1. Accessing Flow Execution Records

To troubleshoot a flow:

  1. Open Integration Hub

  2. Select the Flows tab

  3. Filter by Flow or Date Range

  4. Select the failed Execution

An execution represents every time a Flow is triggered.
​

Execution details include:

  • Status (Success / Failed)

  • Number of attempts (Retries)

  • Triggering mechanism (e.g., Scheduler, Journey Initiator)

2. Viewing Detailed Execution Information

Selecting an execution opens the Execution Details page.
​

This page contains:

2.1 Step Logs

Shows each task executed in the flow, including:

  • Inputs

  • Outputs

  • Task execution order

  • Serialized data used during transformation
    ​

2.2 Execution Logs

These logs reveal:

  • Event-level errors

  • Transformation exceptions

  • Adapter response issues

  • Runtime failures

Example excerpts:

Error occurred during transformation

These logs help identify where in the flow lifecycle the failure occurred.

3. Hyperlinked IDs and Log Navigation

Integration Hub automatically detects IDs inside logs and converts them into clickable links.

When clicked, they navigate directly to the Logging Centre and filter logs by correlation ID or object ID.
​

Hyperlinking provides fast contextual investigation without manually filtering logs.

4. Using the General Logs (Logging Centre)

The Logging Centre provides tenant-wide visibility into system logs.
​

It supports filtering by:

  • Correlation ID

  • Timestamp

  • Flow execution

  • Integration service

This is essential for full root-cause diagnosis when Step Logs or Execution Logs reference deeper internal issues.

5. Required Permissions for Flow Troubleshooting

To access Integration Hub and Flow Execution details, the following permissions are needed:

Permission

Purpose

Integration Flows : Flow Execution Read

View execution summary

Integration Flows : Flow Execution Details Read

View task-level logs and inputs/outputs

Logging Centre : Access

View system-generated logs

Event Ingress permissions

For event-based initiators

Full permission reference:
​

6. Monitoring Live Activity & Execution Limits

Integration Hub provides a Live View showing:

  • Real-time flow execution counts

  • Tenant execution limits

  • Cooldown periods when limits are exceeded
    ​

This helps diagnose issues arising from throttling or overuse.

Did this answer your question?