Every write to your CRM (a call log, a popup, a late recording) is a job you can see on the connection's Activity tab. If the CRM is down or refuses a write, the call waits and is sent again, so a CRM outage doesn't lose calls.
What happens when a write fails#
| Situation | What Edesy does |
|---|---|
| The CRM is down, times out or answers with a temporary error | Retries automatically: after 10 s, 30 s, 2 min, 10 min and 30 min, six attempts in all (about an hour) |
| The CRM rejects the write for good, for example an invalid field | Stops and marks the job failed, with the CRM's reason |
| The CRM stops accepting the connection (password change, access revoked, keys rotated) | Marks the connection Reconnect needed and emails the workspace owner. Calls keep waiting for up to 3 days and are logged once you reconnect |
| LeadSquared's rate limit is reached | Waits a few seconds and sends it then. Waiting doesn't use up retry attempts |
Calls you place from the CRM still go through while a connection waits to be reconnected; only their logs wait.
The Activity tab#
For each job you see the call, the kind of write, its status, how many attempts were made, the CRM's response code and the last error. Failed jobs have a Send again button, which sends the job now with a fresh set of attempts.
A call is missing from the CRM#
- Open the Activity tab and find the call.
- If it failed, read the CRM's reason, fix it (for example a missing field or permission) and click Send again.
- If the connection shows Reconnect needed, reconnect it. Waiting calls are logged straight after.
- If the call isn't listed, check that it was on a forwarding number or placed from the CRM. Other calls aren't sent to CRM connectors.