We are currently tracking an incident where some users are receiving a permission error while saving a segment. Our Development Team is working on a path to resolution and are targeting to hot-fix this incident by end of day today. We will provide another update around 3:00 pm EST (UTC-5).

 

====================================

**Update**

Monday, November 3rd, 3:20 pm EST (UTC-5)


Our Development Team continues to work on this resolution and are still targeting to deploy this hot-fix by end of day. The next scheduled update will be around 6:00 pm EST (UTC-5).


====================================

**Update**

Monday, November 3rd, 6:20 pm EST (UTC-5)


Our Cloud Operations Team confirmed the hot-fix was applied to our Production Environment.

 

====================================

**Update**

Monday, November 3rd, 7:04 pm EST (UTC-5)


Our Cloud Operations Team has identified a false positive and a small percentage of clients failed deployment of the hot-fix. Our Development Team is closely working with them to resolve this in full. We are unable to provide an ETA, but the next scheduled update will be 10:00 am EST (UTC-5) on Tuesday, November 4th, 2014.

 

====================================

**Update**

Tuesday, November 4th, 10:00 am EST (UTC-5)


Our Cloud Operations and Development Team continue to work towards resolution, however no ETA is available. The next scheduled update will be around 1:00 pm EST (UTC-5).

 

====================================

**Update**

Tuesday, November 4th, 1:00 pm EST (UTC-5)


Our Development Team continue to work on a hot-fix that will address the small percentage of clients still experiencing the issue. There is no ETA available but the next scheduled update will be around 4:00 pm EST (UTC-5).

 

====================================

**Update**

Tuesday, November 4th, 4:00 pm EST (UTC-5)


Our Development Team continues to work on this resolution. We are unable to provide an ETA, but the next scheduled update will be around 10:00 am EST (UTC-5) on Wednesday, November 5th, 2014.

 

====================================

**Update**

Wednesday, November 5th, 10:10 am EST (UTC-5)

Our Development Team is currently reviewing a fix for this incident. We are currently unable to provide an ETA for when this fix will be applied. The next update will be at approximately 1:00 pm EST (UTC -5)


====================================

**Update**

Wednesday, November 5th, 12:55 pm EST (UTC-5)

Our Development Team is still reviewing a fix for this incident. We are currently unable to provide an ETA for when this fix will be applied. The next update will be at approximately 4:00 pm EST (UTC -5)


====================================

**Update**

Wednesday, November 5th, 4:00 pm EST (UTC-5)

Our Development Team continues to review the fix for this incident. We are currently unable to provide an ETA for when this fix will be applied. The next update will be around 10:00 am EST (UTC-5) on Thursday, November 6th, 2014.


====================================

**Update**

Thursday, November 6th, 10:00 am EST (UTC-5)

Our Development Team is working to fully test a fix for this incident. We cannot at this time provide an ETA. The next update will be at approximately 1:00 pm EST (UTC -5)


====================================

**Update**

Thursday, November 6th, 1:00 pm EST (UTC-5)

Our Development Team is still testing a fix for this incident. We cannot at this time provide an ETA. The next update will be at approximately 4:00 pm EST (UTC -5)


====================================

**Update**

Thursday, November 6th, 4:00 pm EST (UTC-5)

Our Development Team continues to test a fix for this incident. We cannot at this time provide an ETA. The next update will be at approximately 10:00 am EST (UTC-5) on Friday, November 7th, 2014.


====================================

**Update**

Friday, November 7th, 10:00 am EST (UTC-5)

Our Development Team is still working to fully test the fix for this incident. We cannot at this time provide an ETA. The next update will be at approximately 1:00 pm EST (UTC-5)


====================================

**Update**

Friday, November 7th, 1:00 pm EST (UTC-5)

Our Clouds Operations Team is targeting to hot-fix this incident by end of day today. We will provide another update at approximately 4:00 pm EST (UTC-5)


====================================

**Update**

Friday, November 7th, 3:00 pm EST (UTC-5)

Our Cloud Operations Team has confirmed that the fix has been applied to our Production Environment and the issue is now resolved.