← Back to My app shows an error. What do I do?
Why is my result empty?
Short answer
Check that you sent a token, that it has access, that you called the vault's own host, and that a search names the vault.
Before you start
A read, a list or a search that answered with nothing in it, and the request you sent.
Words used here (3)
- record
- A record is one piece of data with its own address, such as a person, a place, a thing or a note.
- AI vault
- An AI vault is a small vault that stands for your AI; your AI reaches only the vaults you grant it.
- vault's address
- A vault's address is the web address that names one vault, made from the vault's name, such as https://example-name.gilb.com/vault.
Steps
Check that the request carries a token.
Send the header Authorization: DPoP followed by the person's token, with a new DPoP proof, on every call. With no token the caller counts as no one, and no one gets anything from a vault that is not public.
More about this
A DPoP proof is a short signed note your app makes for one request, naming its method and address (RFC 9449). Reading is closed by default: a caller gets only what a grant lets them read, and a refusal is quiet. A search with no token, in a vault that is not public, answers 200 with count 0; a record read answers 404. Checked on production on 2026-11-11, with no token: GET https://id.gilb.com/base/search?q=card answered count 0 and complete true. A header that holds something that is not a token is not quiet: it answers 401 Malformed access token: Invalid JWT.
Compare a caller who has access with one who has not.
Send the same request as a caller who can read that vault and as one who cannot. If only the first gets the data, the data is there and your caller lacks a grant: ask the vault's owner for access.
More about this
A refused read is told the same thing as a missing record, on purpose, so no one learns what exists: 404 for one record, no rows or count 0 for a search. Listing a whole vault you may not read answers 403 vault target denied. An app's server reads only what its AI vault was given; the answer on how an app's server reads its own vault shows how. A test of one caller alone cannot tell no data from no access.
Call the vault's own host.
Send reads and writes of a vault's records to that vault's own host, such as https://<name>.gilb.com, and use the whole record address that a listing or a create gave you.
More about this
The platform looks for a record only on the host the request names; it does not look on other hosts. So an id taken out of its address and put on another host finds nothing: a read answers 404, and a write sent through https://id.gilb.com answers 403 vault target denied. On a platform you run on your own computer, the host comes from the Host header, not from the address you typed. Send the vault's host, for example -H Host: veda.gilb.com with a call to http://127.0.0.1:8787. A Host the server does not serve answers 404. A detail address such as /base/t/<Type> on the wrong Host answers 404 while the list beside it still works.
Name the vault in a search.
Add vault=<the vault's address> to GET /base/search when you search a vault other than your own. A search that names no vault searches the vault of the host you call, and on https://id.gilb.com it searches your own vault, so it can answer a clean count 0.
More about this
Checked on production on 2026-11-11, with no token: GET https://id.gilb.com/base/search?q=card answered count 0, and the same search with vault=https://appbuilder.gilb.com/base, a vault anyone may read, answered 167. The option is vault, not pod: an option the search does not know answers 400 querystring must NOT have additional properties. A search answers only record addresses (ids), 20 a page, never the records; read each one at its address.
Deeper
Also asked:
Why is my result empty when I know there is data? A read you may not make looks the same as no data: 404 or count 0. Check that you sent a token, that it has access, that you called the vault's own host, and that a search names the vault.
Other ways a list comes back empty. Ended records, records someone deleted, are not in the normal listing: ask for them with lifecycle=ended. A type= with a bare name that no record carries answers 200 with no rows; a type written as t:Name or as a full address answers 400 type_token_unresolved, not an empty list.
If every call answers 401 instead, the proof is wrong, not the data. The proof must name the address you call: on your own computer, build it for https://<the Host you send><path>, without the query, not for the http://127.0.0.1 address you fetched. Otherwise the answer is 401 DPoP proof htu does not match the request URI.
Going through these four checks without finding the cause does not prove the data is fine: the list may not hold every cause.
The full reference is the Developer Guide, GilbPlatform's guide for people who build apps on it, in its chapters Dev.Guide.Addresses, https://appbuilder.gilb.com/base/e/06gkzpwjzhtwb4m72ae1jy3t2c, and Dev.Guide.Errors, https://appbuilder.gilb.com/base/e/06gkzpwxmnxf90zcc3mzc757xg. It can be read with no sign-in, as data for programs and AIs rather than as a web page.
Source: GilbPlatform 498d29a0 (live at https://id.gilb.com/version, read 2026-11-11): src/routes/search.ts:155-186 (searchTargetVault: a signed-in non-owner searches their own vault, anonymous the home vault; "returned 200 with count: 0 ... The reader-set predicate was never the problem; the aim was"), :302-345 (principal from the token; vault= wins; else the routed host's vault; a missing principal fails closed inside searchFindAuthorized (empty result)), :54-139 (schema; additionalProperties false), src/read/search.ts:48 (SEARCH_PAGE_SIZE 20); src/read/entity-uri.ts:20-60 (This function does NOT search other hosts; a husk still resolves, the cross-host shadowing is gone), src/auth/served-host.ts:177-193 (resolveRoutedVaultHost: absent or unregistered Host -> null), src/routes/_http.ts:52-59 (non-disclosure 404), src/routes/vocab.ts:771-773 (/base/t/:Type routed by Host); docs/BASE-DEVELOPER-GUIDE.md (team notes at the same revision, read for the causes, not linked): §16.2 (10820, the list works, the detail is empty; a read of veda.gilb.com), §16.3 (10839), §16.4 (10860, the order of checks, the differential, Reaching the end of that list without a match does not mean the data is fine), §16.7 (10925, htu from the Host; build https://<Host><path>, query stripped), §9.1 (8066, the unaimed search clean zero). Dev.Guide.SignIn (A 06gkzpwhanxrh55sca1pdkxj88) Proof, ProofChecks, Surfaces (401 Malformed access token: Invalid JWT), WhichHost; Dev.Guide.Addresses (A 06gkzpwjzhtwb4m72ae1jy3t2c) Host (403 vault target denied through id.gilb.com), CannotReach (403 list); Dev.Guide.Reading (A 06gkzpwp39x2q3dxgj4ytavpvg) Ended, Type; Dev.Guide.Errors (A 06gkzpwxmnxf90zcc3mzc757xg) Answer07, Answer12, Answer17, Answer23; Dev.Guide.AppAccess Read (404 same as missing) (2026-11-11, all 200; read for agreement, not copied). Public reads, no token, 2026-11-11: https://id.gilb.com/base/search?q=card -> 200 count 0 complete true; ?q=card&vault=https://appbuilder.gilb.com/base -> 200 count 167; ?q=vault&pod=x -> 400 querystring must NOT have additional properties. Rows: DeveloperGuide.DiagnoseEmptyResult (cause 4, the husk, is stale at 498d29a0), SetHostHeaderForDetailCalls, BuildProofForRequestHost.: with no token a search answers count 0 only in a vault that is not public; with vault= a public vault it answered 167 (the read above, and step 4).: the two phrases are not app or platform words, so no quotes. Example 2: the address is quoted, so <Type> is not read by a shell as a redirect (applied on Kai-Zen's word).
For developers
curl
aimed-search.sh
# The same search, without and with vault=. No token: only a vault anyone may read answers.
curl -s "https://id.gilb.com/base/search?q=card"
# {"total":{"kind":"exact","value":0},"count":0,"ids":[],"pageSize":20,"complete":true,"next":null}
curl -s "https://id.gilb.com/base/search?q=card&vault=https://appbuilder.gilb.com/base"
# {"total":{"kind":"exact","value":167},"count":167,"ids":["https://appbuilder.gilb.com/base/e/...", ...]}
curl
local-host-header.sh
# On a platform you run on your own computer, name the vault in the Host header.
curl -s -H "Host: veda.gilb.com" "http://127.0.0.1:8787/base/t/<Type>"
Checked against GilbApp d529620.