Symptoms: Sluggish responses from Outlook after Digital-Clay is installed, or occasional freezing.
Some things to know:
ClayOutlook integrates with Outlook events and therefore runs whenever an Outlook contact/task/appointment is changed or deleted. If Outlook folders or the Outlook connection to Exchange is slow or prone to occasional slowdowns, then ClayOutlook may cause the problem to appear worse since it has to perform synchronization of data and retrieve data from Outlook/Exchange.
However, there are some background tasks as well that may affect Outlook performance:
At startup, ClayOutlook runs several tasks such as searching for and synchronizing changes in Outlook, loading cached data, and synchronizing with ClayCentral.
All of these tasks may cause slow or bad connections to be slower, and may occasionally affect Outlook response times when there are many items to process (especially the startup procedure).
If the problem only happens at startup or once every few days then this is to be expected.
If the problem is recurring and happens several times a day, there are several possible techniques for handling this:
Make sure your PST/OST files are not too large. Generally, anything above 3-4
GB can start impacting performance and cause slowdowns. Check the size of your folders and files using the Mailbox Cleanup tool, and make sure you are auto-archiving old data. See also:
Reduce the size of Outlook Data Files
Lower the interval for all three background tasks mentioned previously (Tools/Options). Set each timer function to the highest amount of minutes that you can handle (depending on the function and how often you think it necessary). This can reduce the amount of background work for ClayOutlook, and/or help in cases when there are only periodical Exchange connectivity issues.
Microsoft Exchange related issues:
If Exchange keeps getting disconnected, this may cause occasional freezing while Outlook attempts to reconnect due to ClayOutlook background requests. Outlook usually displays Exchange connectivity in its status bar. Check for Exchange issues, server issues, and networking problems such as bad cables and wireless hardware.