I have a Logic App with Twitter connector that searches for tweets with a keyword. It has been working fine but now it suddenly started failing.
When I look at the output of the Twitter connector, below is the body it returns.
"body": {
"status": 500,
"source": "https://twitterconnectorce8207a3c04d4ebdbf35f4e3fdcee1a4.azurewebsites.net/search/tweets?Query=AisChinaSupport&MaxResults=20",
"message": "An error has occurred."
}
Related
I am trying to use Group By clauses in Azure Logic Apps for querying a single partition which has 1.5m documents.
I can run the query that is coded in the Logic App in the Cosmos Data Explorer without issue:
[{
"AreasProcessed": 1,
"TotalProperties": 1286,
"status": 500
},
{
"AreasProcessed": 45,
"TotalProperties": 0,
"status": 400
},
{
"AreasProcessed": 2275,
"TotalProperties": 2399469,
"status": 200
}]
However, when I run the query in the Logic App, I get the following error:
Continuation token is not supported for queries with GROUP BY. Do not use FeedResponse.ResponseContinuation or remove the GROUP BY from the query.
I have enabled Pagination and Asynchronous Pattern on the Logic App.
The full error on the logic app is below, can anyone help me please?
{"error": {
"code": 500,
"source": "logic-apis-westeurope.azure-apim.net",
"clientRequestId": "4d6a4cdb-8969-4dd7-b382-90929c7ec829",
"message": "BadGateway",
"innerError": {
"status": 500,
"message": "Continuation token is not supported for queries with GROUP BY. Do not use FeedResponse.ResponseContinuation or remove the GROUP BY from the query.\r\nclientRequestId: 4d6a4cdb-8969-4dd7-b382-90929c7ec829",
"error": {
"message": "Continuation token is not supported for queries with GROUP BY. Do not use FeedResponse.ResponseContinuation or remove the GROUP BY from the query."
},
"source": "documentdb-we.azconn-we.p.azurewebsites.net"
}
}}
As far as I know, azure team has integrated "Document Explorer", "Query Explorer", "Script Explorer" features as part of "Data Explorer". So "Data Explorer" is the best way to do the query. I'm not sure azure logic app uses the same backend with "Query Explorer" or "Document Explorer", but it seems the logic app doesn't use the same backend with "Data Explorer". I think it is the reason why you can run the query in "Data Explorer" on portal but can not run the query in logic app.
For this problem, you can create a azure function and do the query with code in the function. Then call the function in your logic app. Here is another post which is similar to your problem(but not same) for your reference.
I just started building a webhook following the documentation. I created a sample web api application and published to IIS with a valid url accessible from the internet.
I created a webhook on out authorize.net sandbox account and set the url. I am able to call the POST api method from inside the postman. But when I try to ping the webhook I get error as follow:
https://apitest.authorize.net/rest/v1/webhooks/70884522-6fe8-4e72-9c7e-15bf2b30f778/pings
{
"status": 500,
"reason": "PING_FAILED",
"message": "The ping operation failed with the status code 403",
"correlationId": "5d136ce8-406f-442e-9118-fdde36946d87",
"details": [
{
"message": "Error occured in connecting to the endpoint:http://staging4.dancecompgenie.com/api/Values/Post "
}
]
}
Here is the url on my server.
http://staging4.dancecompgenie.com/api/Values/Post
I am able to successfully call this url in postman and get the result.
I appreciate if you can help me solve the problem.
Im trying to connect Logical Apps with Text Analyzer however i'm seeing this error:
This is the body of the Output:
{ "error": { "code": 502, "message": "The remote name could not be resolved: 'supportticket.cognitiveservices.azure.com'", "source": "logic-apis-northeurope.azure-apim.net", "path": "forward-request", "clientRequestId": "343d9512-c398-4544-a3ec-bbdd26ad22bf" } }
Not sure how to fix it, seems like its on azure end.
Contacted Azure chat support they forwarded me here for a resolution
I'm trying to implement an app according to the stages written in:
https://developers.google.com/actions/get-started/
I follow all stages, but there is some problem with connecting the Webhook to the app.
When trying to operate the app and connect to the Webhook, I get the following error in the json file:
"status": {
"code": 206,
"errorType": "partial_content",
"errorDetails": "Webhook call failed. Error: Webhook response was empty."
},
Does anyone know what might be the problem?
I am attempting to use Intune specific beta Graph APIs to assign apps to an iOS managed app protection policy. I am able to create the app policies using the endpoint documented below:
https://graph.microsoft.io/en-us/docs/api-reference/beta/api/intune_mam_iosmanagedappprotection_create
When created via API, the app "deployedCount" is 0 until specific apps are added in the admin console UI.
Now, I am attempting to retrieve apps added to any policy by API using the endpoint documented below.
https://graph.microsoft.io/en-us/docs/api-reference/beta/api/intune_mam_mobileappidentifierdeployment_list
I get a 400 bad request response that appears to say this endpoint either does not exist or is not responding correctly. This seems unlike if I mistyped an endpoint.
Response I receive:
{
"error": {
"code": "No method match route template",
"message": "No OData route exists that match template ~/entityset/key/navigation with http verb GET for request /MAMAdmin/MAMAdminFEService/managedAppPolicies('T_338de6df-386d-4f1b-a51c-a0d189c61722')/mobileAppIdentifierDeployments.",
"innerError": {
"request-id": "79514f29-4dca-48a5-a2de-5d14138577d7",
"date": "2017-02-08T17:46:52"
}
}
}
Response if I mistyped:
{
"error": {
"code": "BadRequest",
"message": "Resource not found for the segment 'asdfasdf'.",
"innerError": {
"request-id": "e86d84ab-f062-4780-af3c-9afae6e7bc82",
"date": "2017-02-08T18:53:29"
}
}
}
Hello this is Alemeshet Alemu from MSFT.
Sorry, the API documentation is a bit out sync. Could you try with $expand?
GET /managedAppPolicies/{managedAppPoliciesId}?$expand=mobileAppIdentifierDeployments
Alemeshet Alemu (MSFT)