When an integration problem needs your firm to act, Chronicle emails your administrators once, lists the problem under Needs attention on that integration’s Overview and in a banner on your dashboard, and clears it after the next sync runs clean. This article covers who gets the email, where to find open problems, how to fix each cause (signed out, a broken mapping, a missing permission, a blocked automation, and Neos Microsoft 365), and when a notice clears.
Who gets the email and how often
Every active administrator and account owner on your Chronicle account receives the email, from Chronicle Support. Replying to it reaches our team.
Each problem is emailed once. Chronicle checks hourly and waits for repeated failures (at least three within two hours) before it raises a notice, so a single failed record does not email you.
If a problem is fixed, clears, and comes back more than 7 days later, you get a new email.
The email subject is the problem title. The email explains what is happening, what to do, and has a button that opens the integration’s settings.
Problems that only Chronicle can fix, and temporary provider outages that heal on their own, do not email you.
A sign-out or a broken mapping pauses syncing for that connection until you fix it. Everything already in Chronicle stays safe. For other problems, syncing continues and only some updates are not getting through.
Find open problems
Open problems stay listed until they clear, so you can find a notice again after the email is gone.
Administrators see a banner on the Chronicle dashboard titled An integration needs your attention, with the fix for each problem and a button that opens the integration’s settings.
In Settings > Integrations, open the integration. The Needs attention panel at the top of the Overview tab lists each problem with a count of how many need a decision. Each row has one button: Reconnect, Fix mapping, Open Sync, or Review (for clients with no match or storage folders that need a choice). The panel is hidden when nothing needs a decision.
The Sync tab shows failed records. A record that failed for a problem you can fix shows the same plain title as the notice.
Fix the problem
Find the title from your email or the Needs attention panel below, then follow its fix.
The notice says an integration signed Chronicle out, for example “Box signed Chronicle out”
Chronicle’s sign-in to the provider was rejected. This usually happens when the person who connected the integration left, changed their password, or lost access in the provider. Syncing is paused until you reconnect.
In Settings > Integrations, open the integration and click Reconnect in the Needs attention panel. A Reconnect window opens with the connection controls.
Sign in again. For Box, Dropbox, SharePoint / OneDrive, and Atticus, authorize Chronicle with an account that can still reach your client folders. For Salesforce, click Reconnect again and sign in as a Salesforce administrator, then choose the integration user and click Finish setup.
Syncing resumes once the sign-in works. Chronicle also retries a parked connection every hour for 14 days, so a provider outage can recover on its own. If you received the email and the connection comes back, you get a second email saying the integration is back on. Chronicle waits for a second rejection at least an hour after the first before it asks you to reconnect, which keeps a brief provider outage from triggering a request. If you reconnect storage with a different account, linked client folders must be visible to it or document sync reports them as missing.
The connection panel shows “Salesforce connection failed”
Chronicle can no longer sign in to Salesforce, so syncing is paused. The person who authorized the connection may have left, changed their password, or lost access.
In Settings > Integrations, open Salesforce.
In the Needs attention panel, click Reconnect, then click Reconnect in the window that opens.
Sign in as a Salesforce administrator, choose the integration user, and click Finish setup.
The Salesforce user Chronicle connects as cannot edit a field Chronicle writes to, so those updates are not getting through. Ask your Salesforce admin to assign the Chronicle Integration User permission set (named Chronicle_Integration_User in the notice) to that user, or give the user edit access to the field named in the notice. Syncing continues for everything else. Connect Salesforce to Chronicle shows where to assign the permission set.
A Salesforce automation or validation rule is rejecting Chronicle’s updates
One of your own Salesforce flows, validation rules, or triggers is refusing the update, and the notice names it when Salesforce reports a name. Ask your Salesforce admin to review that automation so it accepts updates from the user Chronicle connects as.
Neos isn’t letting Chronicle use something
The Neos user Chronicle connects as is missing a permission, and the notice names the action and area. Ask your Neos admin to give that user the permission. Connect Neos to Chronicle lists the permissions the connecting user needs.
Neos can’t file documents because its user isn’t connected to Microsoft 365
Neos files documents through Microsoft 365. The Neos user Chronicle connects as must be a licensed Microsoft 365 user and connected to Office 365 inside Neos. When Chronicle finds this, it turns off document, hearing and CE sync for Neos. Fix the user in Neos, then in Chronicle open the Neos Connection panel and click Check again. When it shows Microsoft 365 connected, turn those switches back on, because a successful check does not turn them on for you. Connect Neos to Chronicle shows how to choose Connect now for the Office 365 connection, and Use the Neos integration covers the document and calendar behavior.
A custom field in your Clio sync mapping no longer exists
A field your mapping writes to was deleted in Clio. Until you fix it, Chronicle leaves that one field out and keeps everything else syncing.
In the Needs attention panel, click Fix mapping. The mapping page opens on Client fields with the broken row highlighted.
Pick the field that replaced it, or remove the row if you no longer need it.
A Clio matter stage, practice area, or matter type your sync uses no longer exists
A stage, practice area, or matter type you chose in the Clio integration settings was deleted in Clio, which pauses Clio syncing. Open the Clio integration settings in Chronicle and choose the stage, practice area, or matter type you use now.
Chronicle can’t read Social Security numbers from your Filevine SSN field
The Filevine field you chose for the SSN is a reference field, which Filevine’s API always returns empty, and syncing is paused. In Chronicle’s Filevine settings, set the SSN lookup to Contact record, or pick a plain text SSN field. Connect Filevine to Chronicle covers the SSN lookup.
After you fix it
For most problems, the records that failed while the problem was open do not retry on their own. In the integration’s Sync tab, click Resync, then choose Failed only to send what was waiting. Resync integration data explains the scopes, and Check integration sync status shows how to confirm the result.
When a notice clears
A notice clears by itself when Chronicle sees the problem is gone, and you do not need to dismiss it.
For a sign-out, it clears as soon as the sign-in works again, either because you reconnected or because Chronicle’s hourly retry succeeded.
For every other problem, it clears after the next sync of that kind runs with no failures. A mapping field that Chronicle is skipping stays flagged until you fix or remove the mapping.
If the affected sync stays switched off, the notice clears after 24 hours without new failures.