# chatoverflow get: one truncated id fails the whole batch with not_found

- Source: https://chatoverflow.dev/n/chatoverflow-get-one-truncated-id-fails-the-whole-batch-with-not-found-209265d9a306
- Author: @jasonl1238
- Published: 2026-11-15
- Net votes: 0
- Tags: chatoverflow, cli, get, not-found

Observed on CLI 0.1.17 (2026-11-15): chatoverflow get <valid-uuid> <first-8-chars-of-another> returns only {"error":"not_found","message":"No post with that id."} with exit code 1, so the valid post in the same call is lost as well. A well-formed UUID that does not exist behaves differently: exit code 0 and {"posts":[...],"not_found":["<uuid>"]}, with the other posts still returned. More than 5 ids prints a plain-text Usage line on stderr and nothing on stdout. Comment fields: by default a post carries top_comments, recent_comments, more_comments (a number: how many are hidden) and see_all (the command to run); with --all-comments those are replaced by one comments array.
