Discussions
Categories
ProductExportEndpoint returns status 500 "Please contact Responsys support team"

Hi team,
I'm implementing invocation without data. ProductExportEndpoint returns status 500
message "Responsys failed to process the request at this time due to internal error. Please contact Responsys support team."
.
Could you please advice some fix options?
Here are several requests I made.
Request 1: Data size was 3. The request param was ?limit=0&offset=1000. The request was made around 1666689120 (Tuesday, 25 October 2022 09:12:00 GMT).
Method:GET
Headers:
Authorization : Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJjM2U1Mzg4NC1iZGE5LTQ3YjMtOTBkYS0zNmI0OWJiZTUwY2IiLCJleHAiOjE2NjY2ODkxOTgsImlhdCI6MTY2NjY4OTEzOCwiaXNzIjoiNzVkNWY2ZGItMThmNS00OGE3LThiYTUtYTg2ZTQ3Y2U3NWViIiwiby5hLnAuY3RlbmFudElkIjoiODA4MzQiLCJzdWIiOiI2OTg0MjBjOC1kMGM0LTQyYTQtYjRiNS1iMWI5NzE3ODk3MmUifQ.vDQQF2bBhhcyQ6FclesrGETu6juJLXLLr1lklEJqmuw
Content-Type:application/json
DATASET-ID:3f8e8b10-4df1-41fb-a12b-adf1f88259fc
INVOCATION-ID:0a933ae6-898f-474d-9d2b-2df0bec54ac3
OMC-ID:c3e53884-bda9-47b3-90da-36b49bbe50cb]
Request 2: Data size was 3. The request param was ?limit=0&offset=3. The request was made around 1666689600 (Tuesday, 25 October 2022 09:20:00).
Method:GET
Headers:
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJjM2U1Mzg4NC1iZGE5LTQ3YjMtOTBkYS0zNmI0OWJiZTUwY2IiLCJleHAiOjE2NjY2ODk2NzYsImlhdCI6MTY2NjY4OTYxNiwiaXNzIjoiNzVkNWY2ZGItMThmNS00OGE3LThiYTUtYTg2ZTQ3Y2U3NWViIiwiby5hLnAuY3RlbmFudElkIjoiODA4MzQiLCJzdWIiOiI2OTg0MjBjOC1kMGM0LTQyYTQtYjRiNS1iMWI5NzE3ODk3MmUifQ.EMGYCU2QFgBZI0_5eCk7iUsxJgpLyJx_1uT5RTbJJj4 BasicAuthUsername: BasicAuthPassword: Headers:map[Content-Type:application/json
DATASET-ID: 26288580-c88b-4dd2-85bb-94c1425cbb58
INVOCATION-ID: 01a44b8b-e9d3-470b-89ca-45a0b984f65a
OMC-ID: c3e53884-bda9-47b3-90da-36b49bbe50cb
Request 3: Data size was 3. The request param was ?limit=0&offset=2. The request was made around 1666687560 (Tuesday, 25 October 2022 08:46:00).
Method:GET
Headers:
Authorization:Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJjM2U1Mzg4NC1iZGE5LTQ3YjMtOTBkYS0zNmI0OWJiZTUwY2IiLCJleHAiOjE2NjY2ODc2MzYsImlhdCI6MTY2NjY4NzU3NiwiaXNzIjoiNzVkNWY2ZGItMThmNS00OGE3LThiYTUtYTg2ZTQ3Y2U3NWViIiwiby5hLnAuY3RlbmFudElkIjoiODA4MzQiLCJzdWIiOiI2OTg0MjBjOC1kMGM0LTQyYTQtYjRiNS1iMWI5NzE3ODk3MmUifQ.vI3KFDI7rogaCJ1TwtutrUUVQDA6NXzP6SQQ3F_ywls
Content-Type:application/json
DATASET-ID:c5611276-c894-4e81-825f-55ca21f0575c
INVOCATION-ID:c285a8f0-3076-4e3d-9a24-e1cc3bf220de
OMC-ID:c3e53884-bda9-47b3-90da-36b49bbe50cb
Max Butch Size is set 2.
Program events are Scheduled Filter > Issue Coupon > Set Data > End.
Scheduled filter uses the Run filter.
Here is the filter RIID without Pass.
Docs:
Best Answer
-
Hi,
During the service save configuration process, when AMS call's the service's save configuration URL endpoint, the app should send back the configuration status along with the record definition.
There are special record definition fields (input/output parameters) that must be sent with every service instance configuration.
inputParameters
appcloud_row_correlation_id
outputParameters
appcloud_row_correlation_id
appcloud_row_status
appcloud_row_errormessage
Please make sure appcloud_row_correlation_id is the first entry input/output parameter.
I've validated for the above program that the app stage's instance configuration shows different order. appcloud_row_correlation_id is not in the first position.
Existing Instance with incorrect position of appcloud_row_correlation_id, appcloud_row_status and appcloud_row_errormessage.
"recordDefinition": { "inputParameters": [ { "dataType": "Text", "unique": false, "name": "EMAIL_ADDRESS_", "width": 500, "required": false }, { "dataType": "Text", "unique": true, "name": "appcloud_row_correlation_id", "width": 40, "required": true } ], "outputParameters": [ { "dataType": "Text", "unique": false, "name": "PASS_ID", "width": 50, "required": false }, { "dataType": "Text", "unique": false, "name": "PASS_URL", "width": 100, "required": false }, { "dataType": "Text", "unique": true, "name": "appcloud_row_correlation_id", "width": 40, "required": true }, { "dataType": "Text", "unique": false, "name": "appcloud_row_status", "width": 10, "required": true }, { "dataType": "Text", "unique": false, "name": "appcloud_row_errormessage", "width": 5120, "required": false } ] },
correct ordered format.
"recordDefinition": { "inputParameters": [ { "dataType": "Text", "unique": true, "name": "appcloud_row_correlation_id", "width": 40, "required": true }, { "dataType": "Text", "unique": false, "name": "EMAIL_ADDRESS_", "width": 500, "required": false } ], "outputParameters": [ { "dataType": "Text", "unique": true, "name": "appcloud_row_correlation_id", "width": 40, "required": true }, { "dataType": "Text", "unique": false, "name": "appcloud_row_status", "width": 10, "required": true }, { "dataType": "Text", "unique": false, "name": "appcloud_row_errormessage", "width": 5120, "required": false }, { "dataType": "Text", "unique": false, "name": "PASS_ID", "width": 50, "required": false }, { "dataType": "Text", "unique": false, "name": "PASS_URL", "width": 100, "required": false } ] },
More detail: https://docs.oracle.com/en/cloud/saas/marketing/ams-develop/Developers/ams/develop/record_definitions.htm
Answers
-
Hi Laxmikant,
Setting appcloud_row_correlation_id to the first entry input/output parameter resolved the error.
Thank you very much for your help!