onQueryFeaturesStatusChanged signal only firing once with multiple queries

[MarkHolm]

I noticed that if you run multiple queries on the same layer at the same time, you only get one signal from onQueryFeaturesStatusChanged, and then you can get both results from queryFeaturesResults from the respective task ids. Is this behavior intended? I would think each query should fire the onQueryFeaturesStatusChanged signal separately.

[LucasDanzinger]

Hey Mark,

Do you get the expected results if you use `queryFeaturesResultChanged` signal instead?

[MarkHolm]

It does, but interestingly it fixed something else at the same time. When you do 2 queries on the same features at the same time, one full and one min, the full one comes back with null attributes. This is the case when using the onQueryFeaturesStatusChanged signal.

Using the queryFeaturesResultChanged signal, this is not the case