It appears as though the /createMessage api does not operate within an atomic transaction. We had iOS enabled in our PW application, but it was not configured. When we posted the JSON to /createMessage with "platforms":[1,3,11,12] we received a 200 HTTPStatus code with a 210 status_code which is an argument error. The status_message indicated that the platform argument had something wrong with it, but in fact we received the toast message in our Firefox browser. So some of the platforms succeeded and at least one platform failed indicated by the 210 status_code.
The question is if some of the platforms succeed and some of the platforms fail what is the recommended approach for handling a status_code of 210? We don't know which platforms succeeded and which platforms failed. If we assume that all succeeded then some platforms will not never get the notification. If we assume that all failed and thus resend it then some platforms will be notified multiple times for a single notification. How should this be handled?
Please sign in to leave a comment.