I'm trying to use the "When an IcM incident is created" trigger in my flow.
This is the code view:
{"type": "OpenApiConnection","inputs": {"parameters": {"$filter": "ParentIncidentId eq null"},"host": {"apiId": "/providers/Microsoft.PowerApps/apis/shared_icm","connection": "shared_icm","operationId": "When_an_IcM_incident_is_created"}},"recurrence": {"frequency": "Minute","interval": 1},"splitOn": "@triggerOutputs()?['body/value']"}
When I test it, I receive this error:
{"statusCode": 400,"headers": {"Date": "Wed, 04 Mar 2026 11:16:59 GMT","Cache-Control": "no-store, no-cache","Strict-Transport-Security": "max-age=31536000; includeSubDomains","x-ms-islandgateway": "_prdil301wusgb0_4","x-ms-igw-tracking-id": "c3a3c156-f023-4c59-814c-74100b25d1c320260304111659_prdil301wusgb0_4","x-ms-ppapigateway": "_prdil301wusgb0_1","x-ms-gateway-clusters": "prdil301wus","x-servicefabric": "NoRetry","x-ms-service-request-id": "c3a3c156-f023-4c59-814c-74100b25d1c3","x-ms-correlation-id": "2ff7c0c1-59fb-4c91-8b1d-8786a7fe4ca7","x-ms-activity-vector": "00.00.IN.05.IN.3R.IN.1D.00","Server-Timing": "x-ms-igw-upstream-headers;dur=1017.0,x-ms-igw-req-overhead;dur=0.2","X-Content-Type-Options": "nosniff","Content-Length": "682","Content-Type": "application/json"},"body": {"error": {"code": "BadRequest","message": "Invalid filter expression. Please refer to aka.ms/icm-search-filter for more details/examples.\n\nInner error: {\r\n \"odata.error\":{\r\n \"code\":\"\",\"message\":{\r\n \"lang\":\"en-US\",\"value\":\"Unrecognized 'Edm.DateTime' literal 'datetime'2026-03-04T10%3A59%3A47.440%2000%3A00'' at '45' in '(ParentIncidentId eq null) and CreateDate gt datetime'2026-03-04T10%3A59%3A47.440%2000%3A00''.\"\r\n }\r\n }\r\n}\n\nSearch incidents URL: https://prod.microsofticm.com/api/user/incidents?$filter=%28ParentIncidentId%20eq%20null%29%20and%20CreateDate%20gt%20datetime%272026-03-04T10%253A59%253A47.440%252000%253A00%27&$top=100"}}}
From the description it looks to me that there is that CreateDate filter automatically added that is not correct.
Is this a bug in the trigger?

Report
All responses (
Answers (