Summary: Use Logs and Data on the Run Detail page to understand why an interface run failed and which records need attention.

Requirements: - You need access to Interfaces. - You need permission to view interface logs. - The interface must have at least one recorded run.

Read Logs and Investigate Failed Runs

Run logs show what happened during an interface run. Use them together with run data when you need to find the first error, understand the impact, and decide what to fix before running the interface again.

Understand logs, runs, and data

• A run is one execution of an interface. It can be started manually, by a schedule, or by another trigger.
• A failed run means BrynQ could not complete the run as expected. The problem can come from source data, authorization, mapping, the target app, or a technical issue.
• Logs are messages written during the run. They help you see the order of events and the exact error message.
• Data shows the records processed in one selected run. Use it to see which scenarios and records were new, edited, deleted, skipped, or failed.
• All logs shows logs from the last 30 days across runs. Use it for a wider pattern check. Select one run when you need the Data tab.

Open the failed run

• In the left navigation, open Interfaces.
• On the Interfaces page, find the interface by name. Use Search for interfaces by name at the top of the page if the list is long.
• On the right side of the interface row, select Insights. The drawer opens with monitoring details for that interface.
• If the Overview tab shows The most recent run encountered errors., select View run in that warning. BrynQ opens the failed run on the Run Detail page.
• If you need an older failed run, open the Runs tab in the Insights drawer, select the Error filter at the top, and choose the run row you want to inspect.

Read the run header and run selector

• At the top of the Run Detail page, check the interface name, run status, start time, duration, trigger, and run ID.
• Use the run ID when you contact support or compare this run with exported logs.
• In the left run selector, choose All logs when you want to search logs from the last 30 days.
• In the left run selector, choose a specific run when you want to review that run's Logs and Data together.
• Use the filter chips above the run list to narrow runs by All, Success, Error, Stopped, or Running.
• Use Load older runs at the bottom of the run selector when the failed run is not in the first list.

Find the first useful error in Logs

• Open the Logs tab on the right side of the Run Detail page.
• At the top of Logs, use the severity chips to focus the list. Start with CRITICAL or ERROR when you investigate a failed run.
• Use Search for logs by message or reload id in the log toolbar to search for a field name, record ID, app message, or run ID.
• Read the earliest relevant CRITICAL or ERROR message first. Later messages can be follow-up errors caused by the first problem.
• If the failed run came from the Overview warning, check whether the page highlights the error that BrynQ identified as the first error in the run.
• Use Export on the right side of the log toolbar when you need to download the filtered log list for analysis or support.

Check affected records in Data

• Open the Data tab. This tab is available when one specific run is selected, not when All logs is selected.
• In the Scenarios table, compare New, Edited, Deleted, Skipped, Failed, and Total for each scenario.
• Select View records at the right side of a scenario row when you need record-level detail.
• In the records view, use Search by ID... to find a specific record.
• Use the filter next to the search field to narrow records by All, New, Edited, or Deleted.
• Select View details on a record row to see the field-level changes for that record.
• Use Open technical view only when support or a technical user needs the raw record data.

Decide what to fix

• If the log names a missing or invalid source value, correct the record in the source app first.
• If the log names an authorization problem, open the interface setup and check Authorization before rerunning.
• If the log points to mapping or field conversion, review the interface Mapping and the affected scenario.
• If the Data tab shows failed or skipped records, inspect those records before assuming the full interface is broken.
• If the error is unclear, use the run ID, exported logs, and affected record IDs when you contact BrynQ support.

Re-run only after the cause is handled

• Use Re-run in the top-right header of the Run Detail page only when the interface is ready to process again.
• Do not use Re-run to test the same unchanged failed data repeatedly. Fix the source data, authorization, mapping, or target-app issue first.
• If the page shows Dry Run, the run is a preview. BrynQ processes data, but does not apply changes to the target system.

More Information

Example: The Personio to Nmbrs Employees interface shows a failed run. In Logs, the first ERROR says that the employee email address is missing. In Data, the Employees scenario shows one failed record. Select View records, search for the employee ID, and open View details. After adding the missing email address in Personio, use Re-run only if the interface should process the employee again immediately.