0

Duplicate http request

Hi Tasker community,

I am hoping someone on here can help me with my issue. I have two Tasker profiles set up to push notifications to my http request. The initial set up was straightforward however, I noticed that my endpoint was receiving duplicate messages, even though there was only one push Notification. I played around with using timestamps variable sets, unique ideas, Automating clearing notifications before duplicate can be sent and recursion. I have not had luck with any of those methods trying to stop the duplicate processing of the same notification to my HTTP request. I am thinking to just set up my end point to block duplicates, but I would much rather prefer eliminating this issue on tasker’s side. Please let me know if there are any suggestions one thing I would like to notice I’ve had this profile running prior with no issue.

Follow

2 replies

Votes Newest Oldest

Can you please export your profile's description (not xml) so I can take a look? Long-click the profile in Tasker->export description Thanks in advance

Comment
JG

image.jpeg

image.jpeg

JG

image.jpeg

That means that the Discord app is creating duplicate notifications in the background. Try to enable the option "Has Reply Action" in the condition and see if that helps. Also, set the option to only trigger on created notifications and not removed ones. Hope this helps.

Comment
JG

This did not help. It actually caused intended messages to not get posted to the webhook. Also i will also note that the traditional set up that I have set up for discord does not work with slack. Which caused me to send the slack message to myself through google join where i then am able to send the message to my webhook. And that also is sending duplicates. So you are saying both apps are sending duplicates?

Yes, apps often send duplicate notifications for various technical reasons. What you can do is store the last notification id and then not send again if the id didn't change?

Reply