Thank you for thinking along @lbendlin
I may have a look what is the most error prone power automate flow in this matter and in there, replace the 'get rows V2' by a execute stored procedure to see if this doesn't produce incoherent responses.
I can't do a execute SQL query, because the database is an on premises database, that I need to access via a gateway.
(I should have mentioned that.)
{
"@odata.context": "https://flow-apim-europe-002-westeurope-01.azure-apim.net/apim/sql/cdfdce37856856d47788fc1936e0c0f0/$metadata#datasets('EUXXXXXXXXX3%2CBE_DB')/tables('%5Bdbo%5D.%5BZ4_TABLE%5D')/items",
"value": []
}
or
{
"@odata.context": "https://flow-apim-europe-002-westeurope-01.azure-apim.net/apim/sql/cdfdce37856856d47788fc1936e0c0f0/$metadata#datasets('EUXXXXXXXXX3%2CBE_DB')/tables('%5Bdbo%5D.%5BZ4_TABLE%5D')/items",
"value": [
{
"@odata.etag": "",
"ItemInternalId": "5b31e381-57fb-47a9-b98c-a39d62f2d1f2",
"ID": 2831,
---
}
]
}
But at the same time I think that if the get rows v2 is able to give something else than the two correct options below, then any other query is likely to do the same. The whole issue might be a result of the setup using a gateway.