Forum Stats

  • 3,678,514 Users
  • 7,128 Discussions
  • 12,055 Comments

Discussions

YELLOW / Intermittent Notification Issues / POD 1 Clients

Anirude-Oracle
Anirude-Oracle Posts: 118 Employee
edited Mar 14, 2014 9:34AM in Eloqua System Status

Our Development Team identified an intermittent issue where transactional (notifications) emails were not being sent. We currently don’t have an ETA to share, but our next schedule update on this incident will be Thursday, November 21st around 4:00 pm EST (UTC -5).

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

**Update**

Monday, November 25th, 11:12 am EST (UTC -5)

Our Development Team is still working on this incident. We currently don’t have an ETA to share, but our next schedule update on this incident will be Friday, November 29th around 2:00 pm EST (UTC -5).

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

**Update**

Friday, November 29th, 1:14 pm EST (UTC -5)

Our Development Team has implemented additional logging to help diagnose this incident. Unfortunately we have still not been able to determine the root cause, and an ETA is not yet available. Our next update will be on Friday, December 6th around 2:00 pm EST (UTC -5).

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

**Update**

Friday, December 12th, 10:46 am EST (UTC -5)

Our Development Team continues to investigate this incident, but we have not identified anything tangible yet. We are not able to provide an ETA and our next update will be on Friday, December 13th around 2:00 pm EST (UTC -5).

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

**Update**

Monday, December 16th, 10:18 am EST (UTC -5)

Our Development Team continues to investigate this incident. We are not able to provide an ETA and our next update will be on Friday, December 20th around 2:00 pm EST (UTC -5).

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

**Update**

Monday, January 6th, 10:14 am EST (UTC -5)

Our Development Team continues to investigate this incident. We are not able to provide an ETA and our next update will be on Friday, January 10th around 2:00 pm EST (UTC -5).

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

**Update**

Monday, January 10th, 10:14 am EST (UTC -5)

Our Development Team continues to investigate this incident. We are not able to provide an ETA and our next update will be on Friday, January 17th around 2:00 pm EST (UTC -5).

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

**Update**

Sunday, January 19th, 7:36 am EST (UTC -5)

Our Development Team identified 4 hot-fixes that should help improve this incident. Today, starting at 7:00 am EST (UTC-5), our Production Team started the hot-fix process. In the new few days, we will re-scope this incident given this change and identify our next steps.  Our next update will be on Wednesday, January 22nd around 2:00 pm EST (UTC -5).

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

**Update**

Sunday, January 27th, 10:53 am EST (UTC -5)

The Development and Production Team were able to hot-fix the 4 incidents. We continue to monitor our logs. Our next update will be on Friday, January 31st around 2:00 pm EST (UTC -5).

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

**Update**

Friday, January 31st, 9:08 am EST (UTC -5)

The Development and Production Team continue to monitor our logs. The hot-fixes introduced did assist in minimizing the overall impact of this incident, but not 100%. Our next update will be on Friday, February 7th around 2:00 pm EST (UTC -5).

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

**Update**

Friday, January 31st, 9:08 am EST (UTC -5)

The Development and Cloud Operation Team continues to monitor situation. We have not received any net new reports of this incident since the hot-fix was introduced.

Post edited by Unknown User on
Tagged: