We are unable to publish the LUIS application. Publish button was disabled. Please find the attached screenshot and suggest on this please.
I have this problem in the afternoons (UK) - wait a few hours and it's fine. I wonder if the system gets overloaded at times.
The reason was session time out. I looked at console and found 400 error which says token is missing. So i signed out and signed back in. It started working. I was able to publish code to any slot specified.
It looks like a bug and microsoft should address this session timeout with auto redirect or a proper message.
Try Browsing/Publishing in Incognito mode / Private Browsing.
There are Caching related issue in luis portal
Every day at about 18:30 GMT we get lots of timeouts and 503 and publishing problems. We decided not to publish during that time.
Today we got more delays than usual
https://azure.microsoft.com/en-us/status/ show no errors in westus (the endpoint we are reaching)
It'd very nice to get a LUIS Status page (and not the global Cognitive Status)
This bug has been around for a while now. Advice from Microsoft support was to:
delete all cookies for luis.ai
sign out of the session
then sign back
in
When you sign in again the publish to production button should be enabled again
Related
I have cloned the click-to-call repository and followed the steps as mentioned. I am able to login with said created user but then get stuck at /rtc API.I got some error in network panel. and "General SSL engine problem in console which is not correct. SSL certificates are all correct." Let me know where i went wrong. Please check the screenshot below :
I have had a talk with nexmo team, they said it is the ssl issue.
https://help.nexmo.com/hc/en-us/articles/207051767-Certificate-for-nexmo-com
Now I am unable to find where to import the certificate to my app?
I am the JavaScript Developer Advocate at Vonage (Nexmo).
You also filed an issue at https://github.com/nexmo-community/client-sdk-click-to-call correct? Thanks for that. I will also post my response here.
From your issue, it looks as if the Conversation Id is not being sent.
We recently merged some changes to the repo.
In your .env file, do you have SUPPORT_PHONE_NUMBER? That should be NEXMO_NUMBER.
Also, when calling the server, previously the code in the client.js around line 34 was application.callServer(); it is now application.callServer(application.me.name);
Let me know if this works for you.
Check with Nexmo - either you are out of balance or your account has been been marked inactive for some reason. Most of the time its because of insufficient balance.
I used my credentials for create 3 api's in morning but when in noon I tried to create 4th one, application loader fire a message "The application account information was incorrect". I tried to login again button getting same error. My AppleId and Password are correct because I am using same account for login in developer account.
I tried to close loader thrice but hand is still empty.Waiting for your precious suggestion.
Updated Answer:
It's working fine for me now, please try again now
Obsolete Answer:
Based on this
https://developer.apple.com/system-status/
and this https://forums.developer.apple.com/thread/90725
It seems that service is down to few users, therefore, keep patience and wait until the issue is resolved by Apple team.
I have the same issue which started about 90 minutes ago. Earlier this morning I had success uploading.
Updated 29 Oct. 0635Z back end services are working for me now.
I'm unable to create a new project in the Google Developer Console. I have a single project there but any attempts to add a new one returns a Forbidden error message in the Activities log window (see http://i.stack.imgur.com/hpGI3.png).
I've tried different project names and changed the data location from US to EU but nothing is working.
Thanks.
I've had the same problem and after a day of hitting my head against it I figured it out.
Basically you need to enable 'Google Developers Console' in the apps section of Google Admin.
Go to admin.google.com
Go to Apps
Go to Additional Google Services
Go To Google Developers Console:
Make sure that that the developers console is enabled for the organisation who is getting the forbidden error message.
Note: If you have to enable it for an organisation or everyone this change can take upto 24 Hours. For me it took about 10 minutes to take effect.
I created a new GAE app, but the Cloud Integration section on the Settings page tells me that "An error occurred when creating the project. Please retry."
I have pressed the Retry button multiple times over a period of many hours, but it's just not working. I found this thread, which repeatedly says that the issue is solved, but it's not resolved for me.
Is anyone from Google monitoring this forum? Can you help?
The only solution seems to be to create a new app, and hope for the best (it worked for me). Sadly, if you delete the problem app, the app-id is lost forever.
This is a bit late, but in case someone else stumbles on this question.
In the google cloud console, activate billing from the Storage>Cloud Storage > Browser tab, then activate / retry under Cloud Integration from appengine.google.com.
I didn't need to create a new app id, when I went that route.
I'm stumped. We have a client who cannot log in to our system and yet we can log in fine using her credentials. She can also log in fine from her friends home.
Upon entering her credentials the screen simply refreshes and nothing happens when in fact she should be brought to a dashboard page. When I monitor the request via the Chrome web developer tools I can see that the dashboard does get requested after log in but then suddenly we're brought back to the log in page.
Now I've cleared her cache, cookies and all other temporary internet files from both IE9 (her default browser) and Chrome. Nothing happens. I've read that changing session names might help but that did nothing either.
The system is using the newest version of CakePHP (2.2.1) and absolutely any help would be appreciated.
This issue has been solved. Turns out this client in particular had the wrong date and time set on her computer. Upon setting the correct date and time, she has been able to log in absolutely fine since.
Thanks everyone for help!