Issue with data not being returned from query in Sanity Studio

I’m having an issue where data is not being returned from a query that is present in our studio. The vision tool returns the data properly from within the studio. When using the sanity client however, no documents are returned for the given type. I confirmed both the project ID and dataset are correct. Is there any way to debug this further? I don’t seem to be getting any error messages or anything of that sort. I also confirmed with a

*

query to return all possible documents and attempted to filter it using javascript rather than the query, the documents are still not present so it does not appear to be an issue with the query. In both dev and deployed environments, the data is present in the studio. Other documents and data types other than this one are returned properly. I confirmed the documents are published. I have edited various documents of this type multiple times from different deploys and re-published them to no avail. Also confirmed that useCdn is set to false. Generated a fresh API key, still persists. Confirmed it is in the CORS URLs as well. No console errors in either studio or page that attempts to retrieve data.

If i attempt to run the query from the command line I get an error:
Which is also no help. This is node v18.12.1

I get this error on both our staging and production datasets

ok, running the query from the studio directory resolves the error and returns the data correctly

the error was previously a 500 internal server error

the sanity client still does not return the data however in our web app

confirmed this issue on a separate dev machine as well to rule out local configuration

Given that other data shows up, what’s most likely happening is the documents are drafts and your client is not picking up on the token you’re providing. If you’re using an env to obscure your token, I’d start by checking there.
It could also be that your client is using a different API version than the one that Vision uses. If you haven’t specified an API version, your client will default to

v1

, which is lacking features of

v2021-03-25

(which is what Vision defaults to).

If you’re using an env to obscure your token, I’d start by checking there.

I’m not sure where the token actually comes into play here now that I’m looking more closely. The data is retrieved server side and I set up the client according to this: https://www.sanity.io/docs/connect-your-content-to-next-js

I set both vision and the client to

2022-10-21

manually

and verified that vision still returns the correct results

Also when I tested the CLI I set this version using the

--api-version

flag

I confirmed that the documents are not drafts also - I edited a few and re-published them. All of them appear to be published to begin with

ok so adding a

token

property to the API config did return the documents now. But why weren’t they there before if they are published?

OK got it - the person that imported this data put dots in the IDs

I believe that is the issue at least?

Ah, yes. If a document is on a non-root path (like

drafts.

or anything else with a

.

) it will only be queryable if you make an authenticated request.

ok thanks for the clarification