I recommend updating to version 2.23.17 or newer.
Slightly older versions may work, but It’s a little hard for me to declare a minimum version since we’re only routinely testing against the versions on our managed deployments (often the latest few versions)
Thanks @Jedd, we’re seeing an error the civil3d 3.1.7 connector and server version 2.23.5 which might be related. I’ll get the server updated and check again.
Extract of the error message for your info
"type":"UserInputError","message":"Variable \"$filter\" got invalid value { search: null, includeImplicitAccess: true, personalOnly: false }; Field \"personalOnly\" is not defined by type \"UserProjectsFilter\".","stack":"GraphQLError: Field \"personalOnly\" is not defined by type \"UserProjectsFilter\".\n at coerceInputValueImpl (/speckle-server/node_modules/graphql/utilities/coerceInputValue.js:134:11
Yep, any time you see a bad input message like this, it’s likely a change a server update is required.
I’ll make @oguzhan aware incase this was not intentional, but I suspect with the recent big changes to workspaces, it would be a lot of effort to maintain backwards compatibility with older servers.
Do let me know if you see issues post update.
I would also suggest going straight to the latest 2.24.X version instead of the version number I quoted, I suspect v3 connectors may still have issues with 2.23.x.
Error message you see makes sense to me because includeImplicitAccess are quite new flag that it is must to checked in connectors.
We are moving quite fast on both web and connectors side. Web team keep adding new graphqls to make some features available in connectors. But we are slightly settling on these changes. I would suggest keep your server version up-to-date as much as possible these days. This won’t be always like this. We will freeze things after 1st of June to not break self-deployed servers.