---
title: "Graph server behavior"
slug: "graph-server-behavior"
abstract: "Overview of graph server behavior including the impact of changes and how the server handles a graph reload and rebuild."
---
# Graph server behavior

In Sitecore Content Hub, your content and its relationships are represented as a graph. When you make changes, such as how entities, members, fields, or relationships are structured, Content Hub refreshes affected items and their dependents so everything remains synchronized. For substantial changes (for example, broad [schema updates](https://doc.sitecore.com/ch/en/users/content-hub/schema-changes-and-inheritance.html "Schema changes and inheritance") involving high-hierarchy entities and entity definitions), consider timing your work during low-traffic hours or planning for the graph rebuild operation.

When your changes affect the entity data model, the graph model is updated and the system applies the change across affected items and related types.

When changes do not affect the entity data model, there is no update but corresponding actions, such as the creation of an audit entry using existing graph data, occur. The following changes do not modify the entity data model:

- Validation changes to an entity definition.
- Representation changes to an entity definition.
- Events not related to direct changes or deletion of entities, entity definitions, and data sources.

## Refresh related content

The following changes reload and refresh the graph contents:

| Changes to | Reload |
| --- | --- |
| Content entity definitions that also affect descendants | All entities in the corresponding entity definition, and all entities in dependent entity definitions. |
| Content entity definitions that do not affect descendants | All entities in the corresponding entity definition, and all entities in child entity definitions. |
| Entities | The corresponding entity, and any descendant entities that inherit information from the affected entity, according to the logic explained in this topic. |

> [!note]
> A graph reload *does not* occur when you are only adding entity members, changing the order of members within a single member group, or updating member labels.

## Rebuild graph relationships

To request a graph rebuild, open a service request for the SaaS operations team in the [Self-Service portal](https://support.sitecore.com/csm). Click **Create Service Request** and, in the left pane, select *Content Hub*. In the **Categories** drop-down list, select *Configuration Changes* and, on the **Configuration Changes** page, click **Rebuild graph for a Sitecore Content Hub tenant**.

During a graph rebuild, updates and search results might be temporarily delayed, jobs can show as pending, and some views might be temporarily inconsistent. Normal behavior resumes automatically when the rebuild completes.

After a graph rebuild, [publish any entities](https://doc.sitecore.com/ch/en/developers/cloud-dev/publish-entities-that-have-changed-within-a-specific-time-period.html) that changed between the time of the entity model update and the completion of the graph rebuild. For example, if there was a change to the entity data model on June 20 at `20:00` and a graph rebuild was scheduled and finished at `23:00` the same day, re-publish entities for the three-hour window on June 20 between `20:00` to `23:00`. An Experience Edge resync might also be necessary.