We are currently tracking an incident where Eloqua Engage Emails with Dynamic Content are showing multiple times on send. Our Development Team is working on a resolution, but our Support Team has identified a workaround. In the interim, please contact our Support Team for assistance.

 

At this time, we don't have an ETA, but the next scheduled update will be Thursday, October 31st around 2:00 pm EDT (UTC -4).

 

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

**Update**

Thursday, October 31st, 3:35 pm EDT (UTC -4)


Our Development Team was able to resolve this incident. We are looking into hot-fixing this and at this time, we don't have an ETA.  Our next schedule update on this incident will be Friday, November 1st around 1:00 pm EDT (UTC -4)


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

**Update**

Friday, November 1st, 12:02 pm EDT (UTC -4)


We are still looking into hot-fixing this and at this time, we don't have an ETA.  Our next schedule update on this incident will be Monday, November 4th around 1:00 pm EDT (UTC -5)


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

**Update**

Monday, November 4th, 11:54 am EDT (UTC -5)


We are still looking into hot-fixing this and at this time, we don't have an ETA.  Our next schedule update on this incident will be around 3:00 pm EDT (UTC -5)


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

**Update**

Monday, November 4th, 3:07 pm EDT (UTC -5)


We are still looking into hot-fixing this and at this time, we don't have an ETA.  Our next schedule update on this incident will be around 6:00 pm EDT (UTC -5)


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

**Update**

Monday, November 4th, 6:01 pm EDT (UTC -5)


We are still looking into hot-fixing this and at this time, we don't have an ETA.  Our next schedule update on this incident will be Tuesday, November 5th around 1:00 pm EDT (UTC -5)


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

**Update**

Tuesday, November 5th, 9:33 am EDT (UTC -5)


This incident was hot-fixed at 9.10 am EDT (UTC-5) on POD 1 and POD 3. Our next schedule update on this incident will be Wednesday, November 6th around 1:00 pm EDT (UTC -5)


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

**Update**

Wednesday, November 6th, 10:54 am EDT (UTC -5)


This incident was hot-fixed on POD 2 as part of the scheduled roll-out and is now considered resolved.