EspoCRM Version 7.4.3
Outlook Integration Version 1.2.9
Outlook integration has been working correctly for a long time on my system but a few days ago I found my Outlook calendar was no longer up to date.
Seems that the Outlook calendar sync had stopped working. CRON job still shows ‘success’ but an access error is reported in EspoCRM log. Emails still sync but pushing contact to Outlook also fails with Error 500.
The issue was resolved by setting up a new Outlook Integration as per the official EspoCRM documentation for Administrators. However, I noticed when generating the new client secret key, I could only make it valid for a maximum of 2 years. The expiry option ‘Never’ (shown below from the documentation) does not appear on my account.
Unless this is unique to my Microsoft 365 account, it would be good if someone could update the Espo documentation to highlight this change and the requirement to generate a new secret key at least every 2 years to keep the Outlook Integration working.
Hope this information may help someone else who encounters this issue.
Outlook Integration Version 1.2.9
Outlook integration has been working correctly for a long time on my system but a few days ago I found my Outlook calendar was no longer up to date.
Seems that the Outlook calendar sync had stopped working. CRON job still shows ‘success’ but an access error is reported in EspoCRM log. Emails still sync but pushing contact to Outlook also fails with Error 500.
The issue was resolved by setting up a new Outlook Integration as per the official EspoCRM documentation for Administrators. However, I noticed when generating the new client secret key, I could only make it valid for a maximum of 2 years. The expiry option ‘Never’ (shown below from the documentation) does not appear on my account.
Unless this is unique to my Microsoft 365 account, it would be good if someone could update the Espo documentation to highlight this change and the requirement to generate a new secret key at least every 2 years to keep the Outlook Integration working.
Hope this information may help someone else who encounters this issue.
Comment