Read the History tab
History lists every item Ovante sent to your CRM, or decided not to send, with the reason in a sentence. Gray means Ovante chose to skip it; red means it failed.
The History tab on the Salesforce and ChabadOne pages lists each item Ovante sent, or decided not to send, newest first. A row that wasn't sent says why in a full sentence, and what to do about it when there is something to do.
Open it
- 1Open Settings → Integrations, and click Open on the Salesforce or ChabadOne CRM card.
- 2Click the History tab.
- 3Filter with All, Sent, Not sent or Failed. Load more shows older rows.
Each row names what happened (Attendee registered, Order completed, Donation received and so on), who or what it was about, its status, and when.
What each status means
| Status | What it means | Its reason reads |
|---|---|---|
| Sent | Your CRM accepted it | Nothing |
| Waiting | It's queued for its first try, or for its next try after one that didn't go through | The last error, if there was one |
| Sending | It's going out now | Nothing |
| Not sent | Ovante decided not to send it, on purpose | In gray |
| Failed | Your CRM refused it, or Ovante couldn't reach it | In red |
A skip is gray because nothing is broken: a rule you set, or a fact about the item, said not to send. No record matched and the connection is set never to create one; several records matched and it's set to update none; the event is kept out of your CRM. A failure is red because something needs fixing: a missing permission, a restricted picklist value, or a duplicate rule set to block.
Send one again
Click Replay on any row that isn't Sent or Sending. It goes out within a minute. Fix the cause first: a failure Salesforce will keep refusing, such as a missing permission, isn't retried on its own.
The health line
The row under Connected, above the tabs, sums it up:
- Syncing, with when Ovante last sent something.
- Syncing with errors, with the latest error and View history.
- Not syncing, with the reason and Reconnect. See Salesforce says Reconnect.
- When
- A connection keeps failing
- Then
- After a long run of failed deliveries in a row, Ovante turns it off and emails the org's owner. A CRM that stops accepting Ovante's sign-in is turned off at the first refusal and waits for you to reconnect.
- When
- A connection is waiting to be reconnected, or a webhook was turned off after failing
- Then
- Ovante keeps a record of what happens meanwhile. Reconnecting, or turning the webhook back on, sends the recent held deliveries.
Good to know
- While a connection is off waiting for a reconnect, Ovante holds new activity in History instead of dropping it. Reconnecting sends what it held from recent days; anything older stays in History for you to replay.
- An edit you make by hand on the People page never shows here, because it never goes out. See A manual edit didn't reach my CRM.