Polyosync Help Center

How can we help?

Browse help articles or contact our support team.

Request Support

What should I do if an external integration causes a business process to fail?

Business processes may depend on external applications, APIs, or connected services. If an external dependency becomes unavailable, rejects a request, or returns unexpected information, the associated process may fail or produce incomplete results. How to investigate an integration-related failure: 1. Open Business Processes in your Polyosync dashboard. 2. Locate the affected process. 3. Review the relevant execution in Run History. 4. Examine recorded errors and execution events. 5. Identify the external service associated with the problem. 6. Review the relevant integration settings where available. 7. Confirm that the external service is operational and that the required authorization remains valid. What can cause an integration failure? Possible causes include expired credentials, revoked permissions, temporary service outages, request limits, incorrect configuration, or unexpected API responses. The exact cause depends on the external provider and the operation being performed. Does an integration failure always mean Polyosync is unavailable? No. A process can encounter a problem with one external dependency while other platform functions remain operational. Should I reconnect the integration? Only if the available information indicates an authentication or connection problem. Changing credentials or integration settings unnecessarily may interrupt other operations. Can I restart the process after the external service recovers? Possibly, but first review whether the previous execution completed any actions. This is particularly important for processes that create records, send messages, or modify information in connected systems. What if the integration appears operational but the process still fails? Review the process configuration and recorded errors. If the problem remains unresolved, contact Polyosync Support with relevant execution details. Do not include API secrets or authentication tokens. Polyosync's execution records can help organizations distinguish integration-related failures from other process configuration or execution problems.