SugarCRM is aware of the situation and its magnitude. We apologize for the impact this has had on your business. We are attempting various efforts to address the symptom globally across the Sugar Cloud hosting environment, as we recognize that walking through each user clearing their browser cache can be an overwhelming task for an administrator. However, those efforts have not produced the results we've expected so far.
That being said, on a case-by-case basis our support team has had consistent success. The first step Support recommends is to have each user clear their entire browser cache related to the Sugar application. As of today, this one action has been working for customers because this weekend SugarCRM ran a Repair and Rebuild on every hosted instance.
In rare cases, the simple two-step approach of Repair and Rebuild then clearing cache has not worked. In those cases, Support found one of the following: 1. The users were clearing cache, but only for a limited time period. It is recommended that each user clears their cache for all time. 2. Rebuild JS Grouping Files has resulted in success for some customers.
If the information in this post does not work for your instance, please file a new case with SugarCRM Support. The agents on staff have access to Sugar Cloud hosted instances and can guide you with steps to get back to a successful state.
Regards, Patrick McQueen Director, SugarCRM Support
SugarCRM is aware of the situation and its magnitude. We apologize for the impact this has had on your business. We are attempting various efforts to address the symptom globally across the Sugar Cloud hosting environment, as we recognize that walking through each user clearing their browser cache can be an overwhelming task for an administrator. However, those efforts have not produced the results we've expected so far.
That being said, on a case-by-case basis our support team has had consistent success. The first step Support recommends is to have each user clear their entire browser cache related to the Sugar application. As of today, this one action has been working for customers because this weekend SugarCRM ran a Repair and Rebuild on every hosted instance.
In rare cases, the simple two-step approach of Repair and Rebuild then clearing cache has not worked. In those cases, Support found one of the following: 1. The users were clearing cache, but only for a limited time period. It is recommended that each user clears their cache for all time. 2. Rebuild JS Grouping Files has resulted in success for some customers.
If the information in this post does not work for your instance, please file a new case with SugarCRM Support. The agents on staff have access to Sugar Cloud hosted instances and can guide you with steps to get back to a successful state.
Regards, Patrick McQueen Director, SugarCRM Support
