This article helps you solve the issues users report most in the helpdesk.

How do I check why an interface failed or is stuck?

1. Open Interfaces and select the interface that failed.
   
2. Check the latest run status, error message, and timestamp in the run overview.
   
3. Use Logs to find the first technical error instead of only the last warning.
   
4. If the run remains stuck, restart the run once and check whether the same error returns.
   

What should I do when a mapping change does not appear in results?

• Confirm the mapping change was saved in the correct environment.
• Check whether the interface uses that mapping version in the active scenario.
• Run a new sync after the change so previous output is not reused.
• Validate one example record in Logs to confirm the mapped value is present.

How do I solve authorization or connection errors?

• Reconnect the source or target app in Connecties if tokens expired.
• Check whether scopes or permissions changed in the connected system.
• Confirm IP allow lists or firewall rules still allow BrynQ traffic.
• Run a connection test before starting a full interface run.

How can I safely request a plan or environment upgrade?

• Create a support ticket with the exact environment name and requested change.
• Include impact, desired timeline, and whether testing is needed first.
• Ask for confirmation when the upgrade is completed.
• Re-run one critical interface after the change to validate behavior.

What information should I include when opening a support ticket?

• Add the interface name, run timestamp, and error message.
• Include one concrete example record that failed.
• Mention what changed recently, such as mapping, authorization, or source fields.
• Share screenshots only when they show a specific error not visible in logs.