Interface IContentRoutingReadiness
Tracks whether this server has completed the per-server initialization required to route front-end content requests — i.e. the caches the content pipeline depends on (published content, URLs, domains) have been seeded.
Namespace: Umbraco.Cms.Core.Routing
Assembly: Umbraco.Core.dll
Syntax
public interface IContentRoutingReadiness
Remarks
During a background unattended upgrade the runtime level transitions to Run
before UmbracoApplicationStartingNotification has finished seeding those caches. Serving content
requests in that window lets an early request observe (and cache) a negative result that then persists
until the process restarts. This signal lets the front-end gate content routing on "seeding complete"
rather than merely on Run.
Properties
View SourceIsReady
Gets a value indicating whether per-server content-routing initialization has completed.
Declaration
bool IsReady { get; }
Property Value
| Type | Description |
|---|---|
| bool |
Methods
View SourceMarkReady()
Marks per-server content-routing initialization as complete. Called once the
UmbracoApplicationStartingNotification and its seeding handlers have finished.
Declaration
void MarkReady()
Remarks
This is a one-way, irreversible transition: there is no way to return to the not-ready state.
Consequently a CoreRuntime.RestartAsync() does not re-open the initialization window — once
ready, the server stays ready for its lifetime. This is intentional; the window only needs gating
during the initial boot / background-upgrade sequence, not on subsequent in-process restarts.