My Oracle Support Banner

Same Response Received via REST API for Different Message Id in Engage (Doc ID 2315017.1)

Last updated on OCTOBER 23, 2017

Applies to:

Oracle Social Engagement and Monitoring Cloud Service - Version N/A to N/A [Release V1]
Information in this document applies to any platform.


On : NA version, Engage

Same response received for different message Id
Inconsistent data is being received in /engage/v1/messages endpoint when using SRM REST API, in particular in both requests below:

receiving the same response:
  "id": "1505735567003000000000001254224610004093",
  "uniqueId": "uid_003000000000001254224610004093",
  "type": "direct_message",
  "resource": {
  "id": 244635,
  "resourceName": "COSMOTE",
  "resourceType": "facebook",
  "externalId": "108137602614701",
  "externalLink": ""

This issue is happening in many cases and it seems that this is caused due to both messages has the same uniqueId.
The issue can be reproduced at will with the following steps:
1. use REST API to retrieve Engage messages
2. receiving same response for different messages

The issue has the following business impact:
Due to this issue, users cannot get consistent data for Engage via REST API


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.