I noticed that the profile snapshot dataset profile_snapshot_export_% is refreshed once a day, approximately at the same time.
My understanding is that it happens on a schedule which names looks similar: Profile-Snapshot-Export-Schedule%. I would like to modify the time when this schedule runs and be able to force the execution of the refresh without waiting until the next day.
I am trying to use this API call from Postman:
curl -X PATCH https://platform.adobe.io/data/core/ups/config/schedules/321d047e-7a9d-47af-bc20-94e072ec1519 \
-H 'Authorization: Bearer xxx' \
-H 'x-gw-ims-org-id: xxx@AdobeOrg' \
-H 'x-api-key: xxx' \
-H 'x-sandbox-name: xxx'
-d '
[
{
"op": "replace",
"path": "/schedule",
"value": "0 0 18 * * ?"
}
]'
where the headers get the appropriate values from my environment.
In the above cURL 321d047e-7a9d-47af-bc20-94e072ec1519 is the id of the Profile-Snapshot-Export-Schedule% for the particular sandbox.
The example above if based on the sample provided in Schedules API Endpoint | Adobe Experience Platform, under the title "A sample request to update the schedule state". I just replace "op": "add" with "op": "replace" and provided the path for schedule.
However, if I am trying to run this in Postman I get this error:
{
"requestId": "XD4Rl9hZivZmFLp2ZIoq8Lb5NnOdgdUU",
"errors": {
"400": [
{
"code": "UPLIB-101204-400",
"message": "The patch operation replace is not supported. Provide a valid patch operation and try again."
}
]
},
"type": "https://ns.adobe.com/aep/errors/UPLIB-101204-400",
"title": "The patch operation replace is not supported. Provide a valid patch operation and try again.",
"status": 400
}
Where am I getting it wrong? What would be the correct API call to modify the schedule to a different time in the day?
Any help would be greatly appreciated.
Thanks.
解決済! 解決策の投稿を見る。
Hi @GabrielaNa1
I'm seeing in that documentation for schedules, that we need to use "add" to update the schedule and not replace in this case. Can you give that a try.
curl -X PATCH https://platform.adobe.io/data/core/ups/config/schedules/4e538382-dbd8-449e-988a-4ac639ebe72b \
-H 'Authorization: Bearer {ACCESS_TOKEN}' \
-H 'x-gw-ims-org-id: {ORG_ID}' \
-H 'x-api-key: {API_KEY}' \
-H 'x-sandbox-name: {SANDBOX_NAME}'
-d '
[
{
"op":"add",
"path":"/schedule",
"value":"0 0 2 * * ?"
}
]'
表示
返信
いいね!の合計
Hi @GabrielaNa1
I'm seeing in that documentation for schedules, that we need to use "add" to update the schedule and not replace in this case. Can you give that a try.
curl -X PATCH https://platform.adobe.io/data/core/ups/config/schedules/4e538382-dbd8-449e-988a-4ac639ebe72b \
-H 'Authorization: Bearer {ACCESS_TOKEN}' \
-H 'x-gw-ims-org-id: {ORG_ID}' \
-H 'x-api-key: {API_KEY}' \
-H 'x-sandbox-name: {SANDBOX_NAME}'
-d '
[
{
"op":"add",
"path":"/schedule",
"value":"0 0 2 * * ?"
}
]'
表示
返信
いいね!の合計
Yes, it worked with "add". Kind of counter-intuitive, because I am not trying to "Add" but to modify, but I'll take it!