I have an Azure AD app which was working fine yesterday. But today, the response from the sign in page (the one with the code param), is returning an error and error_description params, and no code param. The values are:
error: temporarily_unavailable
error_description: AADSTS90090: A
transient error has occurred. Please try again. Trace ID: [unid]
Correlation ID: [unid] Timestamp: 2015-08-12 08:44:06Z
A few Googles says this is a temporary error, which should "go away soon", but given this is an authentication request, I would expect such transient errors to be resolved in seconds, or minutes at a maximum, and this has now been happening for hours.
Questions:
Is this something that happens regularly?
How long should it take to be resolved?
Is there anything (other than display an error message) I can do my end to handle this?
Any further information appreciated.
Related
-When I use AddMemberMessagesAAQToBidder api get error.
Error
<AddMemberMessagesAAQToBidderResponse
xmlns="urn:ebay:apis:eBLBaseComponents">
2022-11-10T13:32:33.168Z
Failure
Sorry, something went wrong. Please wait a moment and try again.
Sorry, something went wrong. Please wait a moment and try again.
10007
Error
Web Service framework internal error.
RequestError
1177
E1177_CORE_APIMSG_19110890_R1
I expecting get value instead of error.
I am getting the below exception and would like to know what is the "SystemTracker" that is mentioned in the exception. Also, the namespace in the message entity and in the System Tracker are different. Why could those be different? One has "stage1c" and the other is "1a". If 1c is a failover for "1a", then could it log exception like this?
Azure.Messaging.ServiceBus.ServiceBusException: Put token failed. status-code: 404, status-description: The messaging entity 'sb://c0000hwabt-stage1c.servicebus.windows.net/becm.job.summary.response' could not be found. To know more visit https://aka.ms/sbResourceMgrExceptions. TrackingId:3123b33a-315a-40d5-a1e7-243b2611335e_G9, SystemTracker:c0000hwabt-stage1a.servicebus.windows.net:becm.job.summary.response, Timestamp:2022-10-20T15:56:04. (MessagingEntityNotFound)
These are set by the Service Bus service for use with correlating logs and troubleshooting from the service-side. They're helpful information to include when opening a support ticket but are otherwise not useful. Your application should treat them as opaque values and not assume any meaning to the client.
I am using Dialogflow ES and once I got the webhook setup, I haven't been having issues. But after a few months, I just started getting a random error. It seems to be inconsistent as in sometimes I get it for a specific web call and other times it works fine. This is from the Raw API response:
"webhookStatus": {
"code": 3,
"message": "Webhook call failed. Error: [ResourceName error] Path '' does not match template 'projects/{project_id=*}/locations/{location_id=*}/agent/environments/{environment_id=*}/users/{user_id=*}/sessions/{session_id=*}/contexts/{context_id=*}'.."
}
The webhook is in GCP Functions in the same project. I have a simple "ping" function in the same agent that calls the webhook. That works properly and pings the function, records some notes in the function log (so I know the function is being called), and returns a response fine, so I know the webhook is connected and working for other intents in the same agent before and after I get the error above.
Other intents in the same agent work (and this one WAS working), but I get this error now. I also tried recreating the intent and I get the same behavior.
The project is linked to a billing account and I have been getting charged for it, so I don't think it is an issue with being on a trial or otherwise. Though the Dialogflow itself is in "trial", but the linked webhook function is billed.
Where can I find what this error means or where to look to resolve it?
After looking at this with fresh eyes, I found out what was happening.
The issue was a mal-formed output context. I was returning the bad output context sometimes (which explained why sometimes it worked and sometimes it didn't). Specifically, I was returning the parameters directly into the output context without the output context 'name' or 'parameters'. Everything looked like it was working and I didn't get any other errors, but apparently, when Dialogflow receives a bad web response, it generates the unhelpful error above.
I have received the following error when trying to save a DSX Scheduled Job:
Job schedule entry could not be created. Status code: 500
Screenshot of the error message:
I've tried about six times over the last few hours and have consistently received the above error message.
Debugging via the browser network inspection tool I can see:
{
"code":"CDSX.N.1001",
"message":"The service is not responding, try again later.",
"description":"",
"httpMethod":"POST",
"url":"https://batch-schedule-prod.spark.bluemix.net:12100/schedules",
"qs":"",
"body":"While attempting to get Bluemix Token from BlueIDToken, unable to retrieve AccessToken, failed with status 400 Bad Request, message = {\"error\":\"invalid_grant\",\"error_description\":\"A redirect_uri can only be used by implicit or authorization_code grant types.\"} Entity: {\"error\":\"invalid_grant\",\"error_description\":\"A redirect_uri can only be used by implicit or authorization_code grant types.\"}",
"statusCode":500,
"duration":666,
"expectedStatusCode":201
}
As per Charles comment, the functionality is working ok now. I guess if this happens to another user some time in the future they should contact support.
According to documentation when trial is expired and user opens the app, a message would be shown. But my app closes after showing splash screen without any message in this case.
There is the same question on the Microsoft's forum, but I can't write anything there (it returns me unexpected error when I try to submit my question) and there is no answer.
I get the following line in my event log:
App failed with error: No applicable app licenses found. See the Microsoft-Windows-Twin/Operational log for additional information.
Additional information:
< Data Name="ErrorCode" >-1058406399< /Data >
This is Microsoft's bug and they promise to fix it. You can get more details on the msdn-forum.