After you connect your Exchange account to Robin, changes should sync both ways between the two systems in seconds. Sometimes changes made in Robin sync to Exchange, but changes made in Exchange do not sync to Robin.
This usually means a firewall, proxy, or other configuration blocks your Exchange server from sending updates to Robin.
What stops the sync
During the initial calendar setup, Robin subscribes to a push notification channel for that resource on your Exchange server. Your Exchange server uses this channel to notify Robin when a calendar changes. This gives faster updates and less load on your service.
When a change happens in Robin, Robin notifies your Exchange server and updates its own copy with the results. This is why Robin-created events can sync correctly while changes from Exchange do not.
Fix outgoing Exchange notifications
- Make sure you allowlisted Robin's service IP addresses.
- Check that your firewall allows outgoing connections for Exchange.
- If you use a proxy, make sure the Exchange server can use it for outgoing traffic.
For guides on this, see MSDN: Push Event Notifications and Proxy Servers.
Note: If you use a proxy, you may need to add the configuration to EWS's web.config, so that EWS can send outgoing push notifications to Robin's syncing service. The server reads this file in order. In most cases, put the configuration at the bottom of the file.