We have been using Oauth with Linkedin for years and recently we have noticed that it randomly will fail with a 500 Internal Service Error for ~1 out of 100 people. It will fail for the same users over and over again even if they had logged in before. My guess is that there is something specific about those users that causes the issue.
I know my oauth setup is working because it works for 99% of users. I probably need a linkedin engineer to weight in on this but anyone else who has had experiences like this would be helpful.
Below is a the result of the calls:
{"errorCode"=>0,
"message"=>"Internal service error",
"requestId"=>"92LHE2E7H2",
"status"=>500,
"timestamp"=>1447360584670},
{"errorCode"=>0,
"message"=>"Internal service error",
"requestId"=>"LZ7BJBW2FS",
"status"=>500,
"timestamp"=>1447360791073},
{"errorCode"=>0,
"message"=>"Internal service error",
"requestId"=>"93EFYRXAF1",
"status"=>500,
"timestamp"=>1447360956028},
{"errorCode"=>0,
"message"=>"Internal service error",
"requestId"=>"RVW4W5CVJU",
"status"=>500,
"timestamp"=>1447361645555},
{"errorCode"=>0,
"message"=>"Internal service error",
"requestId"=>"WFA4NBIAC9",
"status"=>500,
"timestamp"=>1447362398692},
{"errorCode"=>0,
"message"=>"Internal service error",
"requestId"=>"H6G55JYMLR",
"status"=>500,
"timestamp"=>1447363655108},
We noticed the same thing for some of our users. We were able to narrow it down to users who did not have at a minimum "basics" selected for their LinkedIn "public" profile visibility. We have had users for years that did not have a public profile enabled in their LinkedIn profile and we never had any issues until recently - so we are guessing this is a recent CHANGE or BUG on LinkedIn's side. We now capture this and let the user know that either LinkedIn is down or that the user needs to enable their public profile (basics).
Related
I'm a student creating a demo app using your test API, and am getting the following error when querying the flight destination API (eg. https://test.api.amadeus.com/v1/shopping/flight-destinations?origin=PAR&maxPrice=200)
I don't get any error when querying the same location using the flight offers search API, so it's not an issue with my key/secret, and the location is definitely included in the limited test API dataset.
I'm using the ruby gem (https://github.com/amadeus4dev/amadeus-ruby) but faced the same issue testing the API on postman.
Any help appreciated!
{
"errors": [
{
"status": 500,
"code": 141,
"title": "SYSTEM ERROR HAS OCCURRED",
"detail": "Primitive technical error"
}
]
}
I was having the same issue with the flight-deals endpoint. I submitted a request to Amadeus support and got the following reply:
Unfortunately we are currently having some issues with this API in the test environment. Our technical team is currently looking for a solution, in the meantime if you need to use this endpoint, please move your app to the production environment where the API will work as expected....in this environment you will receive a free amount of transactions each month just like in test
I did try going over to a production environment and I'm not getting technical errors (500's) any more. It does require signing up for payment in case you go beyond the free tier of request volumes. Not clear when they will have the test environment up and running.
I created standalone application on node.js authorized in AAD with client/secret with permissions to access groups, sites, directories. I managed to create Teams group and team by Microsoft Graph API but when I tried to fetch sites/root or drives
https://graph.microsoft.com/v1.0/groups/{groupId}/sites/root
https://graph.microsoft.com/v1.0/groups/{groupId}/drive
I received 500 Internal Server Error:
{
"error": {
"code": "generalException",
"message": "An unspecified error has occurred.",
"innerError": {
"request-id": (....),
"date": "2020-01-31T09:15:17"
}
}
}
Is access to sites and drives possible by Graph API with app token?
the error is causing by using "Group.Create","Group.ReadWrite.All" together
Yes it is possible. One possibility here is that if you are attempting to access the drive or site right after creating the team, they may not be provisioned yet. There is some delay that can happen, typically only a few minutes at most.
When you register your Azure Active Directory App, which supported account type are you choosing?
I had exactly the same issue as you, but I've created a new Azure AD App and changed the supported Account type back to the first option and all worked accordingly.
I hope this could help your issue.
Thank you.
I've created a medium application for API access a while ago, and I've been using it to connect medium accounts to my website and let them publish stories from my website. But it stopped working recently, and I can't access my app anywhere. I should mention that my medium account isn't premium, so I've been thinking that's the problem. The thing is I can't find any info anywhere about medium preventing free users from creating apps. This is where I've managed my apps in the past: Link, but now I get 403. Does anyone have any info about this?
edit: What I forgot to say is, when I try to connect my account, I receive the access/refresh token, but then when I try the "https://api.medium.com/v1/me" endpoint I get
{
"errors": [
{
"message": "Application not found",
"code": 6005
}
]
}
I've created a web app with Microsoft Graph API and it has been completed/tested and everything is working as expected. This web app is aimed to create calendar events for our Office 365 users. Right now there are a total of 9 users that calendar events are created for and two of them are having issues.
This is the specific response I get from Microsoft Graph API if I'm creating a calendar event for a user that is having issues:
Message:
{
"error": {
"code": "ResourceNotFound",
"message": "Resource could not be discovered.",
"innerError": {
"request-id": "4d6efba0-fce2-4abe-9f60-be3df8b55d6f",
"date": "2018-08-29T15:26:58"
}
}
}
I know that everything I'm doing is correct as the other seven users have no issues so the issue must be with the office 365 account its self. I've looked into account settings/permissions and everything I've checked is identical to a user that is working.
One of the biggest issues I'm facing with this problem is I don't understand the error its self. When it says "ResourceNotFound" my guess is that it's saying that it can't find the user account even though it does exist.
My question is what should be the next steps be in order to find a resolution? Should I see if I can recreate the mailboxes and transfer the email from the broken account to a new account? Or should I continue to try to find the root problem?
I'm having this daily limit problem with my ruby code when I try to issue a download request. This is a test program so I am running it in my terminal. I just call the ruby file.
I've followed this guide to quickly get into the Google Drive API.My code is pretty similar to that guide other than my scopes which are:
SCOPE = ["https://www.googleapis.com/auth/drive", "https://www.googleapis.com/auth/drive.file", "https://www.googleapis.com/auth/drive.appfolder", "https://www.googleapis.com/auth/drive.metadata"]
The credentials I am using is oAuth Service Key with "other" selected.
This is the line of code making the call.
content = HTTP.get('https://www.googleapis.com/drive/v3/files/' + file_id + "?alt=media").body
This is the error I am getting from the HTTP call.
{
"error": {
"errors": [
{
"domain": "usageLimits",
"reason": "dailyLimitExceededUnreg",
"message": "Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup.",
"extendedHelp": "https://code.google.com/apis/console"
}
],
"code": 403,
"message": "Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup."
}
}
I've followed this link and created all the necessary credentials to get it working, but still have had no success. Google Drive API is also enabled in my project.
How can you fix this error even after you've set up the Google API project and its credentials?
Edit: Wanted to note that I have search and upload working with the same code. Download is the only one that is giving me errors.
All the suggestions given here are not up to the mark . This is a routine error that Drive API throws and can be easily handled .As soon as you get the error , you can again request the Drive API to consider your request by using a strategy called exponential back-off . This ensures that you make a call to Drive API again , after a specified amount of time . There is a documentation about this issue by Google and is a common issue when you send too many requests at a time .Check this link right here, it is the answer to all your problems that you are facing https://developers.google.com/drive/v3/web/handle-errors#errors_and_suggested_actions . And also request an additional Quota from Google Developers Console . Additional quota can be requested under the Quotas tab in Google Developers Console. You might be lacking enough quota to make the request . The details for same are given in the link i posted above. You should create an account and request Quota as being an unauthenticated user your requests won't last long.Use Google OAuth to authenticate yourself into the Drive API.