Skip navigation

Our Development Team identified an issue where transactional (welcome, notification, scheduled report, etc) emails were not being sent and they were able to hot-fix the issue at 3:49 pm EDT (UTC-4).

 

This issue affects users 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, July 30th, 2:55 pm EDT (UTC -4)

 

Our Development Team has identified additional transactional emails (non-marketing) not being sent out from our POD3 client. We are investigating this issue and at this time, we do not have an ETA; but will provide another update around 6:00 pm EDT (UTC-4).

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

**Update**

Tuesday, July 30th, 4:26 pm EDT (UTC -4)

 

Our Development Team was able to resolve the additional issue. Transactional emails are now being sent and we will continue to monitor the situation.

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

We are currently experiencing issues with Landing Pages which have Cloud Components. Our Development Team is currently working on the issue, at this time we have no ETA, but we will provide another update around 11:00 am EDT (UTC -4).

 

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

**Update**

Monday, July 29th, 10:40 am EDT (UTC -4)

 

Our Development Team is still investigating this issue aggressively, we still don't have an ETA; but will provide another update around 12:00 pm EDT (UTC-4).

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

**Update**

Monday, July 29th, 11:37 am EDT (UTC -4)

 

Our Development Team was able to identify a fix for this issue. We are looking to get this deployed into our Production environment in a few hours. Another update will be provided around 2:00 pm EDT (UTC-4).

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

**Update**

Monday, July 29th, 1:51 pm EDT (UTC -4)

 

Our Development Team was able to hot-fix this issue. Our Production environment has been patched and the issue is resolved.

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

As part of the Summer '13 Release, we have added the ability to use Dynamic Content in subject lines. Since Dynamic Content may contain HTML, a content check of the subject line was implemented to warn of invalid HTML and to ensure that deliverability would not be affected. This has had the unintended consequence of causing older subject lines that contain field merge <span> tags to generate validation errors if edited. Note that this does not impact the sending of existing emails. In general, if an email is opened in the editor and the subject line contains any angle-bracketed code such as a <span> tag, you will received a validation error and need to remove it.  

 

To address this issue for field merges, remove the raw HTML <span> code and drag the field merge into the subject line from the field merge browser. The field merge will display properly highlighted, and will safely pass the content check. If you have a need to include any other content in your subject line between two angle-brackets <...>, the only workaround at this point is to create your subject line as Dynamic Content, then drag that Dynamic Content into the subject line as with the field merge case.

 

We are looking at options to relax the content checking in order to avoid any inconvenience.

Advisory: Notification emails sent to internal users are currently not displaying Unicode characters due to an encoding issue. Please note that this does not impact emails sent to external contacts via campaigns or programs, but only internally generated emails such as form and visitor notifications. The issue has been identified and is expected to be resolved shortly. If it remains unresolved by 5:00 PM EDT, a status update will be provided here.

 

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

**Update**

Monday, July 22nd, 2:00 pm EDT (UTC -4)

 

The issue was fixed in Production at 1:52 pm EDT (UTC -4)

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


Due to changes in the Eloqua security model in the last Release, an issue was introduced where Web Data Lookups for Custom Data Objects (Data Cards) are not working. The issue has been identified and addressed by the development team, and it should be fixed in production for all clients within the next few hours. This post will be updated once the issue is resolved. If it remains unresolved by 5:00 PM EDT, a status update will be provided here.

 

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

**Update**

Monday, July 22nd, 5:50 pm EDT (UTC -4)

 

The issue has not yet been patched. An update will be provided tomorrow morning.

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

**Update**

Tuesday, July 23rd, 10:20 am EDT (UTC -4)

 

The issue was fixed in Production this morning at 9:53 am EDT (UTC -4)

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

Due to a security enhancement rolled out in today's Release, some accounts have had their passwords expire. To resolve the issue, please change your password.

 

If the connection still fails, then it has been flagged as having to change on next login. You must then set the 'User must change password at next login?' radio button in the User Details area for that account to 'No. User can maintain existing password.'

Due to a recent change in the Twitter API, the Twitter Widgets available through the Eloqua App Cloud (http://appcloud.eloqua.com/apps/twitter-widgets) are currently unavailable. These widgets include Twitter Profile, Twitter Search, Twitter Favorites, and Twitter List. Any Twitter Widgets currently being used will not show up on a page. This will not effect the page layout and will not prevent the page from loading.


If you are interested in visibility into this, please contact our Support Team. At this time, we are currently working to resolve this issue and migrate these widgets to the new Twitter API. We will provide another update on Monday, July 8th, 2013 around 11:00 am EDT (UTC -4).


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

**Update**

Monday, July 8th, 5:00 pm EDT (UTC -4)

 

We have identified the changes necessary to resolve this issue. An update to these cloud connectors is tentatively scheduled to be released tonight. We will provide another update on Tuesday, July 9th, 2013 around 11:00am EDT (UTC -4).

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

**Update**

Tuesday, July 9th, 1:00 pm EDT (UTC -4)

 

We were not able to release this fix last night, we have tentatively re-scheduled this to be released tonight. We will provide another update on Wednesday, July 10th, 2013 around 11:00am EDT (UTC -4).

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

**Update**

Wednesday, July 10th, 11:00 am EDT (UTC -4)

 

We have released an update to these widgets that resolves the issue. Please note that in order for the widgets to appear on your landing page, you will need to open the cloud component and re-save the configuration. The widgets are stylized differently now, due to the changes in the Twitter API, so we recommend you review the styling of the new widgets compared to the existing style of any pages these may be contained in.

 

Additionally, the Twitter Search Widget configuration now requires a unique ID available from Twitter. To obtain this ID, log into your Twitter Developer account on the Twitter website, and create a new Twitter Search Widget. Once you have created the new search widget in Twitter, you will be provided with embed code from Twitter. The unique ID of this embed code can then be used in the Twitter Search Widget cloud component.

 

We will be updating the User Guides for these cloud components with the new configuration requirements.

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


On July 1st, we had two incidents reported for Performance Degradation and Stuck Data Import queues. After analysis by our support teams, it was determined that the incident resulted from an operating system issue. The operating system 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.

Filter Blog

By date: By tag: