You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 22, 2023. It is now read-only.
Have you double-checked this with an empty CE? The fact that their are exactly 3 control actions is a bit suspicious, and I think that it could be because we accidentally created additional links between some objects that shouldn't be there.
Can you provide a full set of queries (or tpl config file) to create the SoftwareApplication/EntryPoint/ControlAction nodes too?
We tested this a bit more and in an empty CE it doesn't cause the same problem. It's not clear to us if we incorrectly linked some objects in the test CE which are causing more than 1 item to be returned in the join query in the RequestControlAction mutation, or if it's incorrectly matching on a different field.
To reproduce in the api-test:
Result:
Then:
Result:
If we query again:
We get three results
The text was updated successfully, but these errors were encountered: