Entity Removed

This error is reported when an entity exists in the deployed schema but is missing from the schema being deployed.

Entity "product" was removed.

Why Deployment Stops

Removing an entity removes it from the generated GraphQL schema and Studio. Existing queries, integrations, automations, and relationship attributes may still depend on it.

Flexkit does not automatically delete the entity’s existing records from the dataset. After deployment, those records remain stored but are no longer accessible through the generated Flexkit API or Studio. They are orphaned from the active schema.

How to Proceed

Before removing the entity:

1. Find GraphQL operations, Studio configuration, integrations, and automations that reference the entity.
2. Update or remove relationship attributes that target the entity.
3. Export or migrate any records that must remain accessible.
4. Deploy and test those consumer changes while the old entity still exists.
5. Remove the entity from flexkit.config.tsx.
6. Deploy the intentional removal:

flexkit deploy --allow-breaking-changes

If You Need to Preserve the Data

Add and deploy the replacement entity first. Run a migration script that reads the old records and writes equivalent records to the replacement entity, then validate record counts and important fields. Update consumers to use the replacement before removing the old entity.

Do not remove the old entity until the migration and consumer updates are complete. The --allow-breaking-changes option acknowledges the loss of schema access; it does not migrate or delete stored data.

Undoing the Local Change

If the removal was accidental, restore the entity definition and run flexkit deploy again without the acknowledgement option.