There's something wrong with the JSON argument field in the schedule task automation / segmentation automation. We've had our cloud script setup like this with a simple JSON argument below that has worked fine for months. It still works if I run the script on an individual player.
{"specialOffer":1} auto-reformats into "{/"specialOffer/":1}"
Answer by griver08 · Oct 08, 2018 at 10:49 PM
It seem's this issue has been resolved. I was having the same problem last week, but not anymore.
Yep. It looks like the bug was resolved and the fix was deployed last night.
Answer by Brendan · Sep 28, 2018 at 08:55 AM
Can you provide the specific Title ID and Scheduled Task, so that we can have a look?
Sure thing!
Title ID : 70BF
Scheduled Task: "Set Special Offer"
Thanks, and to be clear, are you saying that the script run from this scheduled task does not work, as it cannot evaluate the data passed in? I'll have the Game Manager team look into why it's stringifying the data.
Yes. That's exactly what's happening. Everytime I hit "SAVE", it stringifies it again so you'll eventually end up changing {"specialOffer":1} to "{/////////"specialOffer/////////":1}"
HTTP.REQUEST returning CloudScriptHTTPRequestError even if it goes through 2 Answers
TypeError when trying to declare a call to server.GetPlayersInSegment(); 1 Answer
GetPlayerCombinedInfoRequest no longer includes DisplayName in response 2 Answers
Request timeout 3 Answers
GetObjects/SetObjects InternalError 1 Answer