I created an app a year ago and verified all needed webhooks.
December 14th 2016, some webhooks became unverified, despite of the fact that they were created and valided a year ago. I looked into Podio's status page, nothing happened that day.
I'm the only administrator of the target app and nothing changed since I created the app.
I wrote to support, but the given answer was not helpful.
Anyone had this weird issue or an explaination?
Hook might be un-validated if your service was too slow or down. Here is quote from https://developers.podio.com/doc/hooks
The hook must respond with a 2xx status code. If the status code is
different from 2xx more than 50 consecutive times the hook will return
to being unverified and will have to be verified again to be active.
Additionally, your hook may return to unverified if you do not send
responses in a timely manner. You should handle any heavy processing
asynchronously.
Related
I have made an actions on google app for sending notifications during an event.The problem is sometimes the post request to send notifications is not completed and error 429 is shown as status code. Why is it happening? What if I want to send notification to a 1000 users at once. How should I do it? Can someone please help me? I need the solution as fast as possible. Any help would be highly appreciated.
HTTP 429 error is "Too many requests". This error typically occurs when you make too many API requests at a given time, exceeding quota.
If you are running into quota issues, you may want to update your notification logic to queue each request with a short delay.
You may also want to read the Best practices and limits documentation for push notifications.
Up to 10 notifications per user per day.
Up to 1 notification per user per minute.
I made this URL public a few years ago as a way to retrieve data. It was working yesterday. Today my site is crashing as it relies on this data, but google is now returning a 500 error if I try to retrieve it programmatically (through axios).
https://spreadsheets.google.com/feeds/list/1DLAVN3q758sPohCFeZlVSVRZKXzEser1SIsQnH2mvrw/ogwtdyp/public/basic?hl=en_US&alt=json
I have also created a code sandobox with react to demonstrate: https://codesandbox.io/embed/xjmy9vl2z4
However, I am still able to view the response in the browser if I am logged in.
Did google recently change their API so that it is no longer possible to retrieve data this way? Is there a way to configure my axios request in such a way to continue retrieving this data?
UPDATE:
Issue is being tracked here: https://issuetracker.google.com/issues/131613284
According to the support team: "The engineering team believes they have located the source of the problem and are rolling back to a previous build in order to resolve issue. Please stand by."
https://issuetracker.google.com/issues/131613284#comment109
UPDATE:
It seems like the issue has been resolved by rolling back to a previous build. I am no longer experiencing these issues. The link above, and the code sandbox example are both functioning. Reading the forum, it seems like others are also no longer experiencing issues. If you are still experiencing issues, I would encourage opening another (perhaps more specific) post or issue.
I found a lot of posts about this issue, but none is like mine.
I have a website that subscribes to IG real-time updates. Since some time ago trying to subscribe to new notifications returns the above error. Seems like IG can't reach the callback_url.
Interesting findings while troubleshooting:
I tried to manually (directly) access the callback_url and it works flawlessly.
When I run the site on my local machine and make sure the callback_url is to my server + the verify_token is a valid one then it all works as it should! IG reaches the callback_url.
I used the apigee console to make the subscription request and there it sometimes works.. Meaning - I craft the request to IG API and click Send. If it fails then I click again (I don't change parameters) and then it works..
Web server logs are in line with the results I get (when it complains it can't reach then there's no log of a request).
Does anyone have any tip or suggestion how to fix this?
Thanks!
While chasing my own tail for a solution I also contacted IG support. I described the issue using same description as above.
After 2 weeks suddenly everything started working again. Magic! Suddenly no errors at all! Needless to say nothing has changed on my end (hardware / network / code).
I didn't receive any response from their support, but considering that a previous email to them a few months ago took about 2 weeks to answer then I am quite sure some support guy simply fixed the issue on their side and didn't even bother to let me know what was going on.
This could be related to the fact that they killed most of their real time notifications API.
Anyway, leaving this here so that if anyone encounters a similar issue then just know you may need to email IG support.
We're using notification_key to group multiple devices. Since yesterday we're unable to send a message to a notification_key. The GCM endpoint returns with status 200 but the response body is empty. The GCM diagnostics inside Google Play shows that no message has been sent to the device and we additionally checked that the message does not arrive at the device.
However, sending a message to a single registration_id (one of which is managed by notification_key) works as expected.
We haven't touched the GCM related code on our side and it was working as expected the days before. I would like to know if this error is known and if other apps are affected as well. Also happy to hear from Google if they were any changes in the last few days.
The issue has been resolved by Google. This is the answer I got from the Google Group thread I've created for this issue:
Hi Andreas,
We had a recent issue in the send API, affecting a subset of the
notification_key requests. That issue should be fixed now.
Please try again. If the API is still not working for you please
report back using:
https://support.google.com/code/contact/gcm_dev_support
Thanks,
- Diego
I have a php application using the BigCommerce PHP APi v 3.0, the application sends multiple API request to get some data on the store orders (it's a private application in BC), my problem is that of late more and more request are failing and my application is returning a 500 server error because of it. The behaviour is very odd because at times it works and at others it returns that error... Can anyone help me with this, has this happen to more ppl?
Thanks!
To answer my own question here, here's what i got as a response from BigCommerce support:
Thank you for contacting Bigcommerce and for your report.
The 500 errors you have been seeing in greater number this week last
week are expected as there have been several server performance
issues. A couple due to DDoS attacks, some relating to our object
storage system, and issues with our webhooks queue that specifically
affected the API proxy. We are sorry about these service interruptions
and know that our Technical Operations team and been working hard to
first correct then look to prevent the root issues. Assuming no new
issues crop up we should see a reduction in 500 errors back to more
expected, much less frequent levels.
We do appreciate your feedback on this and for bearing with us while
we work to get things back to normal operating levels. While 500
errors are something that can occur they should not be as frequent as
they have likely been seen this week.