Content data¶
Check whether a website's content catalog is waiting to be re-indexed. The catalog holds the categories, site pages, blog posts and brands that content search and link content draw on.
Tips & tricks¶
Pick the card that matches what you're doing. Each prompt is ready to paste into your assistant.
Is my change live yet?
Changing which content fields are indexed does not reach visitors until the content catalog has been re-indexed. dataFields_updateContentFieldsIndexing schedules that run for you a few minutes out and later edits join it, so there is nothing to start by hand. Use this to see where the run stands.
contentData_getReindexStatus¶
Report whether a customer website's content catalog (categories, site pages, blog posts and brands) is waiting to be re-indexed, which is what publishes saved changes to visitors. Products are a separate catalog with their own tool, productData_getReindexStatus.
| Name | Type | Required | Description |
|---|---|---|---|
websiteUuid | string | Yes | The UUID of the customer's website in Hello Retail. Use website_getInfo to look up available websites, or find it in my.helloretail.com under Settings → Website Settings → Website Unique Id. |
The state field says where the catalog stands:
IDLE: nothing is pending, so everything saved has been indexed.SCHEDULED: a run is queued and has not started. Changes saved until it starts join that run.INDEXING: a run is under way.enqueuedAtis when it was queued, andrerunRequestedistruewhen a change saved after it started is already booked into a follow-up run.
There is no tool that starts a run or brings a scheduled one forward: a run is always scheduled automatically by the change that needs it.