Triggered notification returned 201 but did not receive anything nor it showed in the activity feed
While I was testing the REST API for triggering fcm notifications (via Postman), there's a particular instance where the notification did show up anywhere despite getting a 201 acknowledged response. I checked the Activity feed and
get-notifications
api and couldn't find it anywhere. I'm wondering what could have been the reason and if it's a common occurrence on REST APIs 🤔
transactionId is f2251a9e-c4ed-4c4a-9969-478dd7dffcb3
see screenshot for the postman response9 Replies
FYI: I sent the exact same request a couple of times and they got received successfully, so it could not have been due to a bad request
Hi @cmendoza
Can you please share curl request you used to trigger above event (notification)
Hey @Pawan Jain , thanks for checking.
I sent that particular request via postman, but this should be the equivalent (or atleast similar)
Hi @cmendoza
Thanks for sharing the curl request. I don't think there is any issue in curl
@paweltymczuk Can you please check this transactionId internally
f2251a9e-c4ed-4c4a-9969-478dd7dffcb3
hey @cmendoza 👋
From what I see the jobs for that transaction were not created, meaning messages not sent for the workflow.
But I see that today you've triggered the template successfully 😉 are you still facing some problems?
Yeah, my recent requests have been successful. But that particular request stood out and a little concerning because we were returned a
transactionId
but there's no trace of it in the system. Have you had similar incidents like this in the past? I'm wondering what could have caused it.@cmendoza, you just advanced to level 1!
I would have to dive deeper into the code and this case to understand what might be wrong here, from the first sight it's hard to tell. 🤷♂️
I'll let you know 😉
Thanks appreciate it!