I can't log into Asana with my google account - Just get a 504 gateway timeout error. Any advice? I also can't register an account with a new email address. Tried chrome and incognito window and asana app.
Thanks for getting in contact! We were having some issues with availability through today (especially this morning), and our stability engineers are investigating the issue. We hope to be totally stable very shortly, and we recommend checking our status page at trust.asana.com for live status.
Sorry for the inconvenience, and thank you so much for your patience.
Related
As of this week I am suddenly getting gateway timeout from Graph when my mail search finds no results.
I am using a query like this one:
https://graph.microsoft.com/v1.0/users/shared#notreal.com/mailFolders/AllItems/messages?$search="participants:some.person#fake.com"&$select=from,subject,HasAttachments,Id,SentDateTime&$top=100
This is a Graph query which requests up to 100 emails from the Office 365 mailbox of shared#notreal.com where the sender or receiver includes some.person#fake.com. shared#notreal.com is a mailbox that is shared with the account making the call.
My app is authenticated with the oauth2 authentication code flow and has been granted all necessary permissions.
This has been working for about a year. But starting a few days ago, this query only succeeds if results are found. When no results are found, the query takes 30 seconds, Graph returns UnknownError and the response is 504 with reasonphrase Gateway Timeout.
It seems as though something has changed in the Graph API - or perhaps in the Office 365 API, but I can't find any mention of it anywhere.
Microsoft specifically directs questions about the Graph API to stackoverflow, so here I am. I hope the right people are reading.
Why has this suddenly started happening and how can I fix it?
Update: there are now numerous reports of this issue, confirming that it's at Microsoft's end.
Github issue
We saw this question and were actively investigating this kast week. With July 4th long weekend I hadn't got back to this thread until now.
This issue has been resolved on the back end of the service and you should not be seeing this issue anymore.
Thank you so much for sharing the service issue here.
This issue seems to be resolved on our end now.
Good day guys,
Please, I am working on a project that requires setting up Google Adwords account in order to use the API. I am using the Python Client Library. I am getting a DEVELOPER_TOKEN_NOT_APPROVED error when I run my test application.
After a lot of research on the issue, I figured maybe I didn't set up the production and test accounts properly which I am still struggling with. I really hope you can put me through the process as I am running against time.
Looking forward to your help
Thank you very much.
You need Developer Token from production account, but until approval is pending you need authorize API call only for test AdWords account. You need two different Google accounts. You must get Refresh Token after login to your another Google account for testing purpose.
More info: https://developers.google.com/adwords/api/docs/guides/accounts-overview#test_accounts
I integrated the zendesk Single Sign On using JWT several months ago and experienced no issues with customer authentication until this week. Our support team started receiving complaints from some of our customers this week where users that had logged in (authenticated) with our web app but could not access the Zendesk knowledge base. The issue seems at this point to be related to new user accounts.
I am getting the following error message appended to the URL on zendesk authentication failure:
kind=error&message=Please+use+one+of+the+options+below+to+sign+in+to+Zendesk.
Has anyone run into this issue or know what this error indicates?
The issue might be related to this:
If your Zendesk is closed or restricted, and a user tries to sign in
with a different email than the one in Zendesk Support, their request
will be rejected (see Enabling social and business single sign-on )
The original discussion was removed from zendesk site for some weird reason:
https://webcache.googleusercontent.com/search?q=cache:QjwCf_sEY4oJ:https://support.zendesk.com/hc/es/community/posts/115008094888-Zendesk-SSO-error-Please-use-one-of-the-options-below-to-sign-in-to-Zendesk+&cd=1&hl=ru&ct=clnk&gl=ru
I actually solved this for our installation last night. I finally realised what I was doing wrong. I had only turned on SSO for end-users so when I tired to test it, as an agent, it was showing this error. So turning on SSO also for agents solved this.
Thanks for sharing, Greg! That's a good tip.
Yes, thanks Greg! that resolved my issue with this error as well!
Thanks for sharing your resolution, Greg! Arlen, I'm glad you got it working!
I use API Asana in "MyAsana" to follow my Workspace (Project) in Asana.
The API is used in 10 smartphones from different people to follow the task of projects.
After 2 days, the API does not respond. All applications authorized in Asana do not respond.
I reset the API & it works in MyAsana. and today the same problem.
I have to do a reset and change the API in all phones.
Error is: UNEXEPTED ERROR WHILE CONNECTING WITH ASANA.THIS IS MOST LIKELY A PROBLEM WITH ASANA SERVER. Please try again later.
How can I fix this please?
Asana is currently having some problems with its service and has had to temporarily shut down access to the API while it addresses them. Follow #asana on twitter and you should get a tweet when access is restored.
After running smoothly for an entire year, a 'create' call to the Google Documents List API started giving 403 Forbidden errors.
Other methods work fine with the same access_token parameter. This started around December 7th very consistently across all of our users invoking this call.
This API just recently got a deprecation policy where it will stay intact until April 2015. To be fair, I don't expect the Google Drive team to be actively supporting this API, but wondering if there is a chance that something on the Google Drive transition could be related to this inconsistency.
Is anyone else experiencing unexpected errors on the Google Documents List API? Any clues as to what is going on, and how deep might the issue be?
Thank you!