Test a connection
Check access and distinguish credential failures from workflow or data problems.
A connection test checks whether Strive can use the configured service credentials. Open the connection and run Test. Wait for the result before running the test again. A successful test confirms the checked access at that moment; it does not prove every possible provider action or workflow configuration is correct.
Read failures in context
An authentication failure usually calls for checking the account, credential, expiration, or OAuth consent. An authorization failure can mean the credential is valid but cannot access the requested resource. A service or network failure can be temporary and should not automatically lead to replacing a working credential.
Check these in order:
- Confirm the service and account on the connection's detail page.
- Check whether the connection is pending, revoked, or needs reconnection.
- Confirm that the selected resource is shared with the authenticated account or service account.
- Review the test error and connection activity.
- Correct the specific problem, then run one new test.
When the test succeeds but a workflow fails
Open Workflows from the connection and inspect the affected run. A workflow can fail because of an invalid query, field mapping, destination, or unsupported operation even when the connection works. Check the failing step and its inputs before rotating credentials.
If browsing shows no items, remove search and folder filters and check whether more pages remain. A successful connection can legitimately contain no visible data. Storage search can also return an empty intermediate page while scanning continues.
Use credential maintenance for expired or replaced credentials. For many connections, bulk testing reports individual outcomes so you can focus on failures.