Hi,
We’re having some issues sending push notifications from a service. See attached screenshot. I believe this used to work previously, the first instance of this error I can find in our logs were June 3.
We are using a non-empty, runtime only, cardinality many user object class as input to the Push Notification action node.
Does anyone know what could be the issue here?
Hi! I have tried to look into this, and have some follow-up questions:
The number of recipients usually vary between 50-300, I’m unsure how much it has increased in this period. It seems to fail most of the time, though we have seen it pass some times in this period with 20 or less recipients. We have not been able to recreate this in test, the screenshot is from stage.
I might have to correct myself slightly though, we have logic for sending notifications both from a Service (Scheduled) and from an App (Now). We were able to recreate this in the service, but it seems to mostly be failing In the App with error “celebrate request validation failed”. The Push Notification node receives the same type of input both places.
Do you think it would be worth a shot to loop through the users and trigger Push Notification node once per user instead of in bulk, to see if it just fails on some specific users? Or would that give too much latency for 300 users?
Hi! We have a hypothesis that this fails when the batch of recipients is > 20.
Can you try to batch the recipients into groups of 20 or fewer as a temporary workaround until we can fix the bug? Triggering the Push Notification node once per user would be very inefficient.
I will register an issue with our dev team, and we can hopefully get a fix out pretty soon.
Ok, we’ll call Push Notifications in batches of 20, and will get back to you once we have verified the results in production.
Thanks for the help!
