Monitor Interfaces from the Overview

Monitor Interfaces from the Overview

Summary: Use the Interfaces overview to check whether live interfaces are healthy, when they run, and which run logs or data need attention.

Requirements: - You need access to Interfaces. - You need permission to view interface logs to open Insights, Runs, Logs, or Data for an interface run.

Monitor Interfaces from the Overview

The Interfaces page is the starting point for daily monitoring. It shows each interface, its schedule, its next expected run, and the result of the latest run.

Understand what the overview shows

  • Interfaces are BrynQ connections that move or synchronize data between apps.
  • Live shows interfaces that are active or available for use. Use this view for daily monitoring.
  • Draft shows interfaces that are still being prepared. Use this view when you want to check work that is not live yet.
  • Next run shows when BrynQ expects the interface to run again. If the interface is manual, the row shows Manual instead of a planned time.
  • Schedule shows how the interface is triggered, for example by a schedule, manually, or after another interface.
  • Last run shows the latest known result, such as Successful, Completed, Failed, Stopped, or Never run.

Find the interface to monitor

  • In the left navigation, open Interfaces.
  • At the top of the page, use Search for interfaces by name to find the interface by its visible name.
  • In the top-right view selector, choose Live for production monitoring or Draft for interfaces that are still in preparation.
  • When you are in Live, use Filter in the top filter area to narrow the list by status.
  • If an interface is disabled, open the Inactive section below the active list.

Read the interface row

  • In the Interfaces column, check the interface name and connected apps. This confirms that you are viewing the right source and target setup.
  • In Next run, check whether the interface is planned, Manual, Never run, or delayed with Starts soon.
  • In Schedule, check whether the schedule or trigger matches what you expect.
  • In Last run, click the status badge when you want to open the run history for that interface.
  • On the right side of the row, use Insights to open the monitoring drawer for that interface.
  • Use Run only when you intentionally want to start a manual run. If the interface is active, the run control can show a running or stopping state instead.

Use Insights for a quick health check

  • On the right side of the interface row, select Insights. The drawer opens on the Overview tab.
  • At the top of the drawer, check the interface name, connected apps, status, schedule information, last run, next run, and interface ID.
  • If you see the dry run warning, the interface is running in preview mode. BrynQ fetches and processes data, but does not apply changes to the target app.
  • If you see the in-development warning, treat the interface as not ready for production use yet.
  • In Success rate, check how reliable recent runs have been.
  • In Records processed, check how much data recent runs handled.
  • In Total runs, check how much run history is available.
  • In Records Processed, compare records that were added, updated, deleted, skipped, or failed.
  • In Run Results, compare successful, failed, stopped, and running executions.
  • Use 7d, 14d, or 30d in the chart headers to change the time range.
  • In Recent Runs, select a run row when you need the exact run details.
  • If The most recent run encountered errors. appears, select View run in that warning to open the failed run directly.

Review run history

  • In the Insights drawer, open the Runs tab.
  • Use the filter buttons at the top of Runs to focus the list:
  • All shows every run from the selected period.
  • Success shows successful runs.
  • Error shows failed runs that need review.
  • Stopped shows runs that were stopped.
  • Running shows runs that are still in progress.
  • Read each run row by status, start time, log count, and record count.
  • Select a run row to open the Run Detail page.

Inspect logs and data for one run

  • On the Run Detail page, use Back to interfaces in the top-left header to return to the overview.
  • In the left run selector, choose All logs to see logs from the last 30 days, or choose one run to inspect that run only.
  • Use the filter chips in the left run selector to narrow runs by All, Success, Error, Stopped, or Running.
  • Open the Logs tab to review messages for the selected run. Use Search for logs by message or reload id to find a specific message.
  • Use the Export button on the right side of the logs toolbar when you need to download the visible log data.
  • Open the Data tab to inspect records for the selected run. Use this tab to see records that were new, edited, deleted, skipped, or failed.
  • In Data, select View records for a scenario when you need record-level detail, and use Open technical view when support or technical analysis needs the raw data view.
  • Use Re-run in the top-right header only when you want to start the interface again and the button is available.

More Information

Use the overview first when you need a fast health check. Open Insights when the row shows an unexpected Last run, a delayed Next run, or a status that needs investigation.

Example: If the Personio to Nmbrs Employees interface shows Failed in Last run, open Insights, select View run, and review Logs. If the first error says an employee email is missing, open Data to find the affected record. After correcting the source data, use Re-run only if you want BrynQ to process the interface again immediately.

    • Related Articles

    • Monitor Interfaces from the Overview

      Summary: Use the Interfaces overview to check interface health, recent runs, logs, and run data without opening the full interface editor. Requirements: - You need access to Interfaces. - To open run logs or detailed run information, you need ...
    • Template Interfaces

      Template Interfaces A Template is the blueprint for an integration between two systems. A Template Interface is the finished product of that blueprint, an integration put to work. At BrynQ we work out how two systems should connect up front, the ...
    • Adding Variables to Interfaces

      Summary: Add variables to an interface so users can reuse the same interface with values that can be changed before each run. Requirements: - You need access to Interfaces. - You need permission to edit the interface. - The interface must have a ...
    • Rename, Deactivate, and Reactivate an Interface

      Summary: Rename an interface, deactivate it when it should not run, and reactivate it when it is ready to use again. Requirements: - You need access to Interfaces. - You need Edit interface permission for the interface you want to change. - The ...
    • Rename, Deactivate, and Reactivate an Interface

      Summary: Rename an interface, deactivate it when it should not run, and reactivate it when it is ready to use again. Requirements: - You need access to Interfaces. - You need Edit interface permission for the interface you want to change. - The ...