Troubleshooting: Why Does My Interface Get Stuck on Running?
Summary:
If an interface stays on Running during its first run, shows No activity yet, and cannot be stopped, check the status carefully and contact support with the right details.
Requirements:
- You need access to Interfaces.
- You need permission to view Insights for the interface.
Troubleshoot an Interface That Stays on Running
An interface can show Running before BrynQ has written visible run activity. This is most confusing during the first run, because Insights may still show No activity yet and there may be no logs, run history, or processed records to inspect.
Understand what this situation means
- A run is one execution of an interface. During the first run, BrynQ starts the worker before the first visible run result is available.
- Running means BrynQ currently sees the interface as active. While this status is active, the interface is not ready for another run.
- No activity yet in Insights means BrynQ does not yet have visible charts or run history for this interface. It does not always mean that nothing is happening in the background.
- Stop is only available when the interface allows stopping and BrynQ can safely send a stop request. If stopping is not allowed, the button can stay on Running and the run cannot be stopped from the interface row.
- Do not start the interface again while it is still Running. A second start attempt can make the state harder to investigate.
Confirm the interface state
- 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.
- In the interface row, check the status button. If it shows Running, BrynQ still marks the interface as active.
- On the right side of the same row, select Insights.
- In Insights, check whether Overview shows No activity yet or whether Recent Runs, Run Results, or Records Processed have started to appear.
- Open the Runs tab in Insights. If the tab still shows No runs recorded yet, there is no run detail page to inspect yet.
Check whether Stop is available
- Return to the Interfaces page and find the same interface row.
- Move over the Running status button in the row action area.
- If the button changes to Stop, select Stop only when you want BrynQ to end the run. BrynQ opens Stop 'interface name'? before sending the request.
- If the button stays on Running or shows that the task cannot be stopped, do not keep clicking it. This means the run cannot be stopped from the page.
- Do not deactivate, edit, or re-run the interface to force the status to change. Those actions do not clear a stuck first run and can hide useful information.
Decide what to do next
- Wait a short time if the first run was started only a few minutes ago. Some interfaces need time before activity, charts, or run history appear.
- Contact support when the interface keeps showing Running, Insights still shows No activity yet, and Stop is not available.
- Contact support immediately if the interface has been Running much longer than expected for a first run, or if the status blocks other required work.
Send useful details to support
- Copy the interface name from the Interfaces page.
- In Insights, use Copy interface ID if you can access it.
- Note the approximate time when the first run was started.
- Tell support that this is the first run and that Insights still shows No activity yet or No runs recorded yet.
- Tell support whether the Running button changed to Stop when you moved over it.
- Add the source and target apps if you know them, for example Personio as the source app and Nmbrs as the target app.
More Information
Example:
You start the Personio to Nmbrs Employees interface for the first time. The row on Interfaces changes to Running, but Insights still shows No activity yet and the Runs tab shows No runs recorded yet. When you move over Running, the button does not change to Stop. Wait a short time, then contact support with the interface name, interface ID, start time, and the note that this is the first run with no visible activity yet.
Related Articles
Frequently Asked Questions
This article helps you solve the issues users report most in the helpdesk. How do I check why an interface failed or is stuck? Open Interfaces and select the interface that failed. Check the latest run status, error message, and timestamp in the run ...