When a connection is missing or silent, the cause is almost always one of a small number of things. Working through them in order is faster than searching for error messages.
Troubleshooting sequence
- Confirm the account type. Personal, business, and enterprise accounts often expose different integration sets.
- Check administrator policy. Many connections are disabled by default until an administrator allows them.
- Consider staged rollout. A feature can be generally announced but not yet enabled for every account.
- Check region and data-residency restrictions, which can remove a connection entirely.
- Re-authorise. Tokens expire, passwords change, and permissions get revoked upstream.
- Check the source system's own permissions — the assistant cannot see what your account cannot see.
- Test with a single, unambiguous item before concluding that search is broken.
Silence is not the same as absence
A connection returning nothing usually means scope, not breakage. Confirm what the connection is pointed at before assuming the integration is faulty.
When to escalate
Escalate to the platform vendor when the connection is present, authorisation succeeds, permissions are confirmed, and retrieval still fails on an item you can open yourself. Include the exact item, the timestamp, and the account used.
Questions
Sources
No sources are attached to this record yet, so no factual claims are published for it.