App integration issues often begin after a password change, security update, account switch, or permission adjustment. One service may still appear connected while quietly losing access to the data or actions it needs.
Before removing and rebuilding an integration, confirm which permissions were granted and whether both services are using the expected accounts.
Identify Which Side of the Connection Is Failing
An integration always involves at least two systems. Determine whether the sending app fails to provide information, the receiving app rejects it, or authentication breaks between them.
Look for recent error messages, failed sync records, or connection-status pages inside each application.
Broader technology directory resources may help when researching unfamiliar software categories, but the integration’s own activity log is usually more useful for identifying the failure point.
Run a Small Test
Send one harmless test record instead of triggering a large synchronization. A single contact, file, task, or sample entry can reveal whether the connection still works.
Record the time of the test so you can match it against logs.
Review Permissions on Both Services
Open the connected-app or integrations area in each account. Confirm that the connection is still authorized and that required permissions haven’t been removed.
Some integrations need permission to read data, while others also need permission to create, edit, or delete it.
| Integration Symptom | Area to Inspect | Next Check |
|---|---|---|
| No data arrives | Read access | Source permissions |
| Updates won’t save | Write access | Destination rights |
| Connection expired | Authentication | Reauthorize account |
| Wrong records sync | Scope/filter | Integration rules |
Recheck Authentication After Account Changes
Changing a password, enabling stronger login protection, or switching organization accounts can invalidate an existing authorization token. The apps may need to be reconnected even though neither one is malfunctioning.
Modern account connections often depend on automated verification methods and secure authorization flows. Follow the official reconnect process rather than sharing passwords directly with third-party tools.
If the integration requests broader access than expected, review the requested permissions before approving them.
Inspect Filters, Fields, and Data Mapping
Permissions can be correct while the integration still behaves incorrectly. A filter may exclude new records, or a field name may have changed after one app was updated.
Compare the source fields with the destination fields and run another small test. This is especially useful with CRM systems, spreadsheets, forms, calendars, and automation platforms.
Reading about connected software infrastructure can provide useful background, but the decisive evidence comes from your own mapping rules and integration logs.
Check for Changed Requirements
A service may retire an older connection method or change which permissions an integration requires. If a connection that worked for months suddenly stops, review official release notes or integration documentation.
Don’t assume your original configuration will remain valid forever.
Common Assumptions That Waste Troubleshooting Time
Deleting an integration immediately can erase mappings or settings that would have helped identify the fault. Another mistake is checking permissions on only one service.
People also blame synchronization delays for every missing record. If repeated tests fail completely, waiting longer may not change anything.
Avoid granting every available permission simply to make the connection work. Give the integration the access it genuinely needs, then test the specific action that was failing.
Frequently Asked Questions
Why did an app integration suddenly stop working?
Expired authorization, changed passwords, revoked permissions, service updates, altered fields, or modified integration rules can interrupt an existing connection. Recent account or software changes are useful clues.
Should I disconnect and reconnect an integration?
Reauthorization can solve expired authentication problems, but first record existing mappings, filters, and settings. Removing the connection without documenting them may create extra setup work.
Why does an integration sync some records but not others?
Filters, field requirements, record ownership, permissions, validation rules, or unsupported data types may exclude certain entries. Compare one successful record with one failed record to identify the difference.
Fix the Connection Without Overcorrecting
Start with the smallest useful test. Verify both accounts, inspect permissions, check authentication, and compare mapping rules before rebuilding the integration. If reconnecting becomes necessary, document the existing setup first. That measured approach solves many connection problems without creating a second problem through unnecessary access changes or lost configuration.