Sleep and Timeouts
The reverse connector should include a controlled delay between processing cycles to avoid making unnecessary API requests.
Talk2Sync monitors API call volume by account and may contact you if the implementation generates an excessive number of requests or if the integration should be adjusted.
Recommended Sleep Interval
The recommended sleep interval between reverse synchronization loop iterations is 2 to 4 seconds.
This delay should be applied when the connector completes a processing cycle and is about to start checking for new work again.
Processing Timeout
When the connector is pushing or pulling products, Talk2Sync uses a 30-second timeout for the process. This value may be changed by the platform UX team.
Therefore, the implementation must ensure that the time between API calls within the process does not exceed this timeout. Otherwise, Talk2Sync may consider the process finished.
Important: The sleep interval should balance API usage and processing continuity. Use the recommended 2–4 second delay while ensuring that the overall process does not exceed the applicable timeout.
Recommended Loop
flowchart TD
A([Process synchronization]) --> B[Make required API calls]
B --> C{More work?}
C -->|Yes| D[Wait 2–4 seconds]
D --> A
C -->|No| E([Finish process])
D -.-> F[Keep call interval below timeout]
Next Steps
- Review Implementation for the complete set of reverse connector implementation components.
- Review Query Implementation: Products and Orders for source-system data retrieval.
- Review Store Implementation: Products and Orders for processing incoming updates.
- Review the Reverse Connector Protocol for the complete synchronization loop.