When consuming the Group Forum Open Cloud API, the postId returned by the category post listing may not be the postId that owns newer comments for the same thread.
Observed behavior:
- A post appears in GET …/forum-categories/{categoryId}/posts with a groupForumPostId and commentCount.
- GET …/posts/{thatPostId}/comments returns fewer comments than commentCount, with no further pages (nextPageToken empty).
- The same thread on the website serves newer comments under a different postId in the URL (…/post/{otherPostId}/comment/{commentId}).
- GET …/posts/{otherPostId}/comments returns those newer comments.
- The other postId does not appear in the paginated category post listing.
- GET …/posts/{postId} returns 404 for both postIds.
Integrations that discover posts only via the listing endpoint cannot reach comments on the non-listed postId, even though those comments are visible on the website and readable via the Comments API when the correct postId is known.
Expected behavior
One consistent model, for example:
- The listing includes the postId that receives new comments for the thread, or exposes a link field (e.g. activePostId / threadRootId) to it.
- Or: commentCount and the Comments API for a listed postId include all comments shown on the website for that thread.
- Or: GET single post works and exposes related/continuation postIds.
At minimum: commentCount should match the number of comments returned by the Comments API for the same postId.
A private message is associated with this bug report