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.
Can you provide the specific Title ID and Scheduled Task, so that we can have a look?
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}"
4 People are following this question.
