Polyosync Help Center

How can we help?

Browse help articles or contact our support team.

Request Support

Why did an integration that previously worked suddenly stop working?

An external integration can stop functioning even if it previously worked correctly. This may happen because authentication credentials expire, permissions change, an external provider experiences an outage, or the connected service changes its configuration. Common causes 1. Expired or revoked authorization. 2. Changed passwords or credentials in the external service. 3. Removed permissions or modified access scopes. 4. External API outages or temporary failures. 5. Rate limits or usage restrictions imposed by the provider. 6. Changes to the connected account. 7. Modified workflow configuration. 8. Missing or invalid required data. How to investigate Step 1: Identify the affected integration. Determine whether the problem affects one connected service or multiple integrations. Step 2: Review its connection status. Check the available integration settings for errors, disconnected states, or authorization requirements. Step 3: Review recent changes. Consider whether an administrator changed permissions, credentials, or external account settings. Step 4: Inspect the failed operation. If an automation or AI Employee encountered the problem, review the corresponding execution details. Step 5: Check the external provider. Verify whether the external service is available and whether the connected account remains active. Step 6: Reauthorize if necessary. If the integration requires renewed authorization, follow the supported connection procedure. Use only authorized accounts and approved credentials. Step 7: Test a limited operation. Where supported, perform a low-risk test to verify that the connection works again. Security considerations Never include API keys, access tokens, client secrets, or passwords in support tickets. Do not grant broader permissions than necessary simply to bypass an integration error. When to contact Support Provide the integration name, approximate failure time, affected operation, relevant error message, and whether the issue started after a configuration change. If the problem originates from an external provider, investigation may require checking that provider's service status or account settings.