Skip navigation

After analysis by our support teams, it was determined that the incident resulted from a hardware issue.  The hardware issue has been resolved and production use of your Eloqua service has been restored.  Oracle is also reviewing the monitoring, alerting and standard operating procedures related to the incident.  After these reviews are completed, additional appropriate corrective actions identified during the reviews will be taken.

In our upcoming 2013 Summer Release we will be introducing a new “Completed” status to the workflow. When an active campaign reaches its end date, the campaign will automatically be deactivated and its status will be updated to “Completed”. This will then remove any contacts that are currently members of any campaign step and exit them from the campaign.


Users will still have the ability to view the campaign exit history for 3 months after the end date of a campaign through Settings -> Operational Reports -> Exit History.


Additionally, “Completed” campaigns will now be read-only and cannot be re-activated again.  If you wish to re-purpose the workflow of a “Completed” campaign, you can simply make a copy of the campaign.


For Campaigns which don’t necessarily have an end date, such as Nurture Campaigns, you can continue to follow best practice and future date these campaigns 1 or 2 years out.

There will be a short interruption to all CRM Integrations as we need to patch our integration services.

 

The application will remain available and no data will be lost. Next update will be around 4:00 pm EDT (UTC -4).


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

**Update**

Tuesday, May 21st, 3:40 pm EDT (UTC -4)

 

We have started with all clients on Pod2.


To determine if you are on Pod2:

Log into Eloqua as you normally do

Look at the browser URL once you are logged in

Pod2 URL has the following format - www02.secure.eloqua.com/... (note:  02 included in URL)

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

**Update**

Tuesday, May 21st, 3:45 pm EDT (UTC -4)

 

We have completed patching Pod2. We are now commencing with all clients on Pod3.

 

To determine if you are on Pod3:

Log into Eloqua as you normally do

Look at the browser URL once you are logged in

Pod3 URL has the following format - secure.p03.eloqua.com...... (note:  03 included in URL)

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

**Update**

Tuesday, May 21st, 4:05 pm EDT (UTC -4)

 

We have completed patching Pod3. We are now commencing with all clients on Pod1.

 

To determine if you are on Pod1:

Log into Eloqua as you normally do

Look at the browser URL once you are logged in

Pod1 URL has the following format - www.secure.eloqua.com/...  (note:  no number included in URL)

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

**Update**

Tuesday, May 21st, 4:40 pm EDT (UTC -4)

 

We have just completed patching on all pods. Our integration services will be resuming momentarily.


We thank you for your cooperation during this time.

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

I wanted to give everyone an update for our Segment based Eloqua Insight Reports.


Working with both the Development and Product Management Team, we have concluded that these reports pose a high risk to the integrity of Eloqua Insight. In getting these reports to execute successfully, it created major performance issues in Eloqua Insight. In addition, because a contact receiving an email can come from multiple segments, in one campaign, the report would pick a single segment that the contact was a part of.  This method creates a problem where the data viewed by segment looks inconsistent.  The Product Management Team is working on a better way to represent this data and is open to user feedback on a proposed solution.


In terms of next steps, we will be hiding these reports impacted while our team works towards getting this corrected. If you are interested in visibility into this, please contact our Support Team. At this time, we have no short term ETA on a resolution.


In the interim, you can continue to use Contact Segment Filters and the Campaign Analysis report to help retrieve analytic data. For example, using an additional filter such as ‘open email at least once’ on top of your existing segments to identify which contacts and how many have opened an email.


Kind Regards,


Anirude Gurcharn

Problem Management Team

 

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

**Update**

Monday, February 3rd, 3:14 pm EST (UTC -5)

 

We apologize for not closing the loop on this advisory, and want to thank everyone for point this out. We were able to resolve this advisory with our 2013 Fall Release.

Please be aware, the Email Deliverability Tests feature is currently offline and we are working with our third party vendor to get this operational. Another update will come around May 2nd, 1:00 pm EDT (UTC-4).

 

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

**Update**

Thursday, May 2nd, 1:45 pm EDT (UTC -4)

 

We are still working with our vendor on resolving this. Another update will come on May 3rd around 1:00 pm EDT (UTC-4).


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

**Update**

Thursday, May 2nd, 1:45 pm EDT (UTC -4)

 

We just got confirmation from our vendor this is resolved.

We are aware that some clients are experiencing errors when opening a form. While the Development Team is actively investigating the issue, we encourage all clients to please continue to file a case with our Support Team and we will get these forms fixed.

 

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

**Update**

Wednesday, May 1st, 9:00 pm EDT (UTC -4)

 

The Development Team has identified a solution for this incident. The fix is currently going through our hot-fix process and we are targeting to get this into our production for May 2nd. Another update will come at May 2nd, 4:00 pm EDT (UTC-4).


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

**Update**

Thursday, May 2nd, 3:15 pm EDT (UTC -4)

 

This issue was hot-fixed and resolved at 12:15 pm EDT (UTC-4).

Some clients are experiencing delays in email deployment. We are working on a solution to clear the email queue as quickly as possible. This issue affects users on Pod3.

 

We will provide another update once the queue starts to clear.

 

To determine if you are on Pod3:

Log into Eloqua as you normally do

Look at the browser URL once you are logged in

Pod3 URL has the following format - secure.p03.eloqua.com...... (note:  03 included in URL)

 

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

**Update**

Wednesday, May 1st, 8:45 pm EDT (UTC -4)

 

The Production Team recycled services which assisted in clearing the queue. They will continue to monitor this service. In the interim, the Development Team will be investigating the root cause.

Filter Blog

By date: By tag: