New issue with CB field Query Drop down and CB Core field ajax Integration

Hello
I have updated to all latest build as of today and got an issue with CB field Query Drop Down

We have this query
When a user had no event or had not yet joined the mentioned group, we had a display of the field description text which explained what to do.

Since updating, the description is not added any longer in the ajax edition on the profile tab (whether inline or modal) and the field itself is no longer available in the profile edit tab

I don't know if it comes from the latest build or a previous one.

The field itself works fine for old users who had already joined groups and chosen events. The mentioned behavior only occurs for new registered users and occurs both in front end AND back end (field not available in backend !)

Could it be some thing with CB Groupjive ?

The query looks fine. What are the display parameters for the query field configured to? Sounds like it's getting an empty display output which is why the field wouldn't be visible.

I have
Show on Profile : 1 line without title
Show on Registration : no
Show on Profile Edit : Yes, 1 line without title
Searchable : no
Required : no

and for CB Core Fields Ajax integration
Display : enable
Strict : disable
Access : registered
Output : inline

Placeholder : text
Additional fields : cb_marketreturn
Add fields titles: 1line without title
update on : nothing

I think it was working fine a couple of weeks ago.
Maybe an update in CB Core Ajax conflicts with the field info display ?

edit :
This is the description text that I use
in the frontend html, the field is displayed with a hidden class :
Maybe the main CB config settings "show empty field" which has changed recently for CB query field ??

The query is resulting in no results. This means the options list for the select field is empty. When this happens the field is hidden, because it's a completely unusable select field. Will add a parameter to let you turn this behavior off.

Thanks a lot
That’s great to provide explanations for the user

It might actually be better to just add a Custom HTML field below your query select field then use CB Conditional with a Query condition to check if they've joined any events. You can then use all the features of a Custom HTML field to display whatever notice you need. Would this be an acceptable solution?

An option to show empty query select just doesn't make any real sense as it's not a usable field and I've concerns it being there would just add a parameter to confuse people.