Problem Definition

Confluence usage is increasing on many large enterprises.
The rate on which a page is modified has increased, as well as the complexity of these pages.

Consider a scenario on which a Confluence page is used as a dashboard, which is updated through an automation using the REST API each 10 minutes.
This means this page is placed on the indexing queue each 10 minutes, but sometimes the new content doesn't need to be searchable immediately.

On a large instance, on which a lot of content is updated/created on a high rate, changes performed by automation tools could overload the index queue.

Having the option to defer an update to be immediately reindexed could be interesting for large instances and complex use cases.

Suggested Solution

It would be interesting to choose if we need to immediately reindex the changed content or if it could be indexed later.
For example, modifying a page through the REST API could provide an option to choose if the page should be reindexed at the time of this modification.

This would be interesting on the scenario where we update a page each 10 minutes, but only need to reindex it once a day.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.