Why did my integration disconnect or stop working after previously working?
An integration that previously worked may stop functioning when its authorization, external account permissions, provider configuration, or service availability changes.
This can happen even when no changes were made directly within Polyosync.
Common reasons
1. An access token expired.
2. A refresh token was revoked or became invalid.
3. The external account password or security settings changed.
4. An administrator revoked application access.
5. The external account was disabled or suspended.
6. Required permissions were removed.
7. The provider changed its API or authorization requirements.
8. An external subscription or service entitlement changed.
9. The connected resource was removed.
10. The external provider is experiencing a service interruption.
What is an access token?
An access token is a credential that allows an authorized application to perform permitted operations against an external service.
Access tokens commonly have limited validity periods.
What is a refresh token?
Some providers issue refresh tokens that allow an application to request renewed access without requiring the user to complete authorization every time.
Not all providers or integrations use the same renewal mechanism.
Does an expired access token always require manual reconnection?
No.
Some authorization mechanisms support automatic renewal.
Manual reauthorization may be necessary when renewal is unavailable, unsuccessful, or no longer permitted.
How to restore the connection
Step 1: Identify the affected integration.
Determine which external service and operations are no longer functioning.
Step 2: Review the available connection status and error information.
Look for authentication failures or authorization-related messages.
Step 3: Verify the external account.
Confirm that the account remains active and accessible.
Step 4: Check whether access was revoked.
Review the provider's authorized application settings where available.
Step 5: Confirm the required permissions.
Ensure the external account still has access to the intended resources.
Step 6: Reauthorize the integration if required.
Use the supported connection management procedure.
Step 7: Test the integration.
Perform a controlled operation and verify the result.
Step 8: Review dependent business operations.
Check whether any affected workflows or processes need attention after the interruption.
Will reconnecting automatically recover missed operations?
Not necessarily.
Recovery depends on the integration, the operation, and whether retry or replay functionality is supported.
Do not assume that missed actions will automatically be repeated.
Can reconnection cause duplicate operations?
Potentially, if an interrupted operation is manually repeated after it has already been processed by the external service.
Check the external result before retrying actions that create or modify records.
Recommended approach
Investigate why authorization stopped working before reconnecting, and verify whether any business operations were interrupted during the outage.