René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Hashnode GraphQL returns stale posts due to Edge caching (latest published posts not visible immediately)","articleBody":"**Summary**\n\nWe are fetching posts from Hashnode GraphQL API (https://gql.hashnode.com/) for our website blog page.\nEven after publishing a new post, the API sometimes returns stale data (old totalDocuments and missing latest post).\nThis looks like an Edge cache issue, where the response is served from cache even though the publication has new content.\n\n**What we expect**\n\nWhen a new blog post is published on our Hashnode publication, the query should return the latest post immediately (or within a predictable short time).\n\nWhat actually happens\n\t•\tAfter publishing a new post, our website still shows old posts\n\t•\ttotalDocuments stays the same (example: sometimes 46 instead of 47)\n\t•\tThe newest post doesn’t appear in posts.edges even when requesting the first page\n\t•\tSometimes after multiple requests or after some time, it starts showing the latest data\n\nSo the response is inconsistent even for the same query + variables.\n\nquery \n```graphql\nquery Publication($after: String, $first: Int!) {\n  publication(host: \"prathamd01.hashnode.dev\") {\n    posts(first: $first, after: $after) {\n      totalDocuments\n      pageInfo {\n        hasNextPage\n        endCursor\n      }\n      edges {\n        node {\n          id\n          slug\n          title\n          publishedAt\n          url\n        }\n      }\n    }\n  }\n}\n```\n\n**Why we think this is Edge caching**\n\nHashnode docs mention that responses are cached at the Edge:\n\n“Almost all responses of queries are cached on the Edge.”\n“Cached data will automatically be purged if you mutate the data.”\n“If you don’t request the field id… it is possible that you get stale data.”\n\nWe are already requesting id fields, but still getting stale results.\n\n**What we tried**\n\n-  Setting cache: \"no-store\" / cache: \"no-cache\" in fetch\n\n- Setting response headers in our Next.js API route:\n\n```graphql\nres.setHeader(\"Cache-Control\", \"no-store, max-age=0, must-revalidate\");\nres.setHeader(\"Pragma\", \"no-cache\");\n```\n\n- Still stale data sometimes.\n\n-  Fetching more posts (first: 20) and sorting by publishedAt client-side\n\n- This works more often but feels like a workaround, not a real fix.\n\n✅ Polling every 15 seconds\n\n- Works but increases request count and is not ideal for production.\n\n\n**Key problem**\n\nEven if we bypass caching on our side, Hashnode still sometimes returns cached/stale data from the Edge, so the newest published post is not visible immediately.\n\n\n**Request / Question**\n\nIs there a way to ensure fresh posts data always comes from Hashnode GraphQL?\n\nFor example:\n\t•\tan option to disable edge caching for specific queries\n\t•\ta recommended approach for “latest posts” use-case\n\t•\ta way to force cache purge on publish/update\n\t•\tor a documented cache TTL / propagation time","author":{"url":"https://github.com/prathamd123","@type":"Person","name":"prathamd123"},"datePublished":"2026-01-16T05:04:08.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/86/support/issues/86"}