On a 409 Name Conflict exception, the response does not contain the ID of the group in conflict, requiring the use of another API call to get the ID of the group with that name. Typically we recommend trying to find the group first, if the group is likely to have been created, but in the instance it is not, then 2 calls are, once again, necessary.
We have also seen instances where the group name search is not returning a valid result, and the logic can never find, nor create the group, causing a critical failure in the logic.
Confirmed this is still an issue as of February 2020.
Need GroupId to be returned in the Create Group API context_info.conflicts. Not feasible to iterate through the results in the Get Groups API when the box instance has >10,000 groups.