Nektar’s design strikes a balance between as efficiency and accuracy. Nektar is tuned to meet the real-world latency requirements for CRM data, without being wasteful of API quotas or compute resources.
Typical end-to-end latency
This table shows the typical end-to-end latency for reading and processing new data and writing it to Salesforce.
|
Average |
Worst-case |
| Creating or updating contacts on Salesforce |
1 hour |
9 hours |
| Creating or updating activities with participants already on Salesforce |
1 hour |
9 hours |
| Creating activities with contacts that need to be created by Nektar |
2 hours |
18 hours |
| Creating Opportunity-Contact relations with contacts already on Salesforce |
1 hour |
9 hours |
| Creating Opportunity-Contact relations with contacts that need to be created by Nektar |
2 hours |
18 hours |
| Merging Nektar-created contacts with manually created duplicates |
25 hours |
33 hours |
What does “end-to-end latency” mean?
- We start the clock when:
- an email is sent or received in a Nektar-monitored mailbox
- an event is added to or edited in a Nektar-monitored calendar
- the manual Salesforce change is made, for self-healing and auto-recall
- We stop the clock when Nektar makes the corresponding change on Salesforce.
Something appears to have taken longer
This could happen because:
- Nektar sync might have been disabled or stopped due to error for the particular user or object at the time of the start-clock event mentioned above.
- Nektar sync was only recently enabled for this user or object, and the initial bulk sync has not completed. These latencies are applicable to ongoing operations, not during bulk sync. The sync status icon is blue during bulk sync and green during ongoing operations.
- Salesforce writes might have been disabled or stopped due to error at the time.
- Salesforce writes were only recently enabled, and it had not completed bulk sync yet.
- Events (including recurring) more than 3 months in the future are only processed by Nektar when they come within the 3 month window.
- Auto-recall. For example if there was no matching account at the time of an email but the account was created later, the account creation is the start-clock event, not the email itself.
- An event was originally filtered out due to a screening rule, but a subsequent edit made it pass. The edit is the appropriate start-clock event, not the creation.
- Salesforce API errors might prevent Nektar writing data for prolonged periods of time. These often occur due to poorly performing Apex triggers or other tools that perform too many API calls to your Salesforce instance.
- In rare circumstances, Nektar, the communication tool’s API service, or Salesforce might have encountered a technical incident at time of the activity. Nektar’s uptime status for the past 30 days is available, as are similar pages for other tools.
Sources of latency
There are three main sources of latency in Nektar: