The api was returning vals tbat dont exist any mkre. I had Townie help me debug but theres still soke kind of issue.
Perfect! Now I can see the full structure of val objects from the API. Based on the response, I can see that there is no "deactivated" property or similar field that indicates whether a val is inactive or deleted. Here are all the properties available on val objects from the API: Core Properties: name - The val's name id - Unique identifier version - Version number code - The actual code content public - Boolean indicating if it's public privacy - "public", "private", or "unlisted" type - "http", "cron", "email", etc. createdAt - Creation timestamp updatedAt - Last update timestamp Metadata: url - Val Town web URL links - Object with API endpoints and module URLs author - Object with author ID and username likeCount - Number of likes referenceCount - Number of references readme - README content (can be null) What's Missing: There is no property like: deactivated deleted active status archived The Issue: If you're seeing vals in the list API that don't exist anymore, this suggests: Caching issue - The API might be returning cached results that include deleted vals Race condition - Vals might be getting deleted between when the list is generated and when you try to access them Permission changes - Vals might have changed privacy settings making them inaccessible API inconsistency - There might be a lag between deletion and removal from the list endpoint Potential Solutions: Check the actual endpoint - Try accessing the links.endpoint URL to see if it returns 404 Use the individual val API - Call the links.self URL to verify the val still exists Filter by updatedAt - You could filter out very old vals if that correlates with the issue Report to Val Town - This seems like an API consistency issue that should be reported Would you like me to modify the API to test which vals are actually accessible vs. which ones return 404s?