Web Trigger sometime not working

MacroDroidDev

Administrator
Staff member
I am now back from holiday, but I do have 100s of emails to work through and for added excitement while I was away a rat has come through my waste pipe in my kitchen and destroyed various bits of plumbing under my sink which is a nice return. So as always I'm going to be working as hard as I can but also repairing various plumbing over the next day or two, so this issue may take some time to properly think about.

It's extremely difficult for me to track these sort of issues without any concrete information as my server gets a very high number of requests constantly. Generally speaking I believe that if the server is returning ok then the request has been made sucessfully to Firebase Cloud Messaging by my server and the failure in this case is likely to be between Firebase Cloud Messaging and the app receiving the notification. This will be particularly difficuly to debug unless I can create this scenario myself.

It would be helpful if one or more users who are seeing this flakeyness can keep detailed records of any failures (times etc) and send me a bug report specifying your unique webhook id, how you are calling the WebHook (e.g. GET or POST, any body and what mechanism you call the API from). This way I can try and find what I can about an individual failure.
 

Endercraft

Moderator
I am now back from holiday, but I do have 100s of emails to work through and for added excitement while I was away a rat has come through my waste pipe in my kitchen and destroyed various bits of plumbing under my sink which is a nice return. So as always I'm going to be working as hard as I can but also repairing various plumbing over the next day or two, so this issue may take some time to properly think about.

It's extremely difficult for me to track these sort of issues without any concrete information as my server gets a very high number of requests constantly. Generally speaking I believe that if the server is returning ok then the request has been made sucessfully to Firebase Cloud Messaging by my server and the failure in this case is likely to be between Firebase Cloud Messaging and the app receiving the notification. This will be particularly difficuly to debug unless I can create this scenario myself.

It would be helpful if one or more users who are seeing this flakeyness can keep detailed records of any failures (times etc) and send me a bug report specifying your unique webhook id, how you are calling the WebHook (e.g. GET or POST, any body and what mechanism you call the API from). This way I can try and find what I can about an individual failure.
Good luck for every issue...

Was that rat sent by Google, by any chance?
 

MacroDroidDev

Administrator
Staff member
Good luck for every issue...

Was that rat sent by Google, by any chance?
I think this is one problem in my life I can't blame Google for. This is more the fault of my messy neighbour who's garden is an absolute state and hence attracts rats.
 

vm53

Member
It would be helpful if one or more users who are seeing this flakeyness can keep detailed records of any failures (times etc) and send me a bug report specifying your unique webhook id, how you are calling the WebHook (e.g. GET or POST, any body and what mechanism you call the API from). This way I can try and find what I can about an individual failure.
As requested I sent you in the bug report a small part of a larger macro, regarding the failure to activate the webhook, or rather it works 1 time out of 3, when it goes well. I hope you can do something. Thanks!
 

vm53

Member
I forgot that by modifying my macro (complete) and using the telegram api instead of the webhooks, this works completely for every command, obviously it is certainly not as convenient and fast as your webhook!
 

MacroDroidDev

Administrator
Staff member
I done a quick test of this late last night and was able to recreate the flakiness issue. Having looked into it, the cause was that the APIs being used for sending FCM have been deprecated and replaced with a new mechanism and they have started to decomission the old API. Since this was clearly a very imporant issue that would affect many users, so I prioritized this over everything else and I have just deployed a new update to my server which seems to solve the problem.

Let me know if you still see issues.
 

MacroDroidDev

Administrator
Staff member
For me it is now complete broken.

When I call the URL, this is the answer:

Request failed - Internal server error: java.io.IOException: Server returned HTTP response code: 400 for URL: https://fcm.googleapis.com/v1/projects/macrodroid-production/messages:send

Sigh.....

Please send me exact details to support@macrodroid.com of how you are calling the macrodroid end point. The messaging format has completely changed so it could be that there are issues that are relevant to the data you are sending or how you are calling it.
 

MacroDroidDev

Administrator
Staff member
Quick update...

The API no longer supports nested JSON to be passed, so my way of handling parameters is breaking the API. I'm working on a fix for this now
 

dborn

New member
Well, I'm getting constant failures now since 18:27 EDT.
Every request returns HTTP/1.1 502 Proxy error.
 

arshit09

New member
it's not working for me as well, when manually visiting the URL in the browser I'm getting "This site can’t be reached". Thank god it's not the issue from my end. I had a fear that I'll need to spend tons of hours debugging the issue.
 

nguyenkimvy

New member
it doesn't work for me:

when i open webhook in browser it say:

This site can’t be reached

trigger.macrodroid.com took too long to respond.
 
As mentioned on title, the web trigger function became very unstable this few days.

Sometime i need to trigger the URL up to 5 times then only the macro will run. But the trigger URL always return "ok".

Btw, i am using LDplayer9, latest version.

Anyone face the same issue?
I have a few macros and even programs I've written on my PC to message back & forth between more than one phone, and they are all failing as of about 12 hours ago, as far as I can tell. Usually when this happens it's only my older desk-bound phone, and an update to MacroDroid has always fixed it. Not today. The phones can't ping each other, and the PC won't send to or receive from either of them. I hope they get this fixed quick.
 

vm53

Member
I confirm that it no longer works since 00.00 Italian time, while before it worked because up until that time I often used the webhook, as I was debugging a new macro of mine.
 
Top