Attribute Removed

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

Attribute "product.mainImage" was removed.

Why Deployment Stops

Removing an attribute removes the corresponding field from the generated GraphQL schema and from Studio forms and views. Existing queries, integrations, automations, or custom Studio configuration may still reference it.

Flexkit does not automatically delete existing values for the attribute from the dataset. After deployment, those values 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 attribute:

1. Find GraphQL operations, Studio configuration, integrations, and automations that reference the attribute.
2. Decide whether its existing values can be abandoned or must be migrated.
3. If the values must be preserved, add and deploy a replacement attribute before removing the old one.
4. Run a migration script, validate the copied values, and update consumers to use the replacement.
5. Remove the old attribute from flexkit.config.tsx.
6. Deploy the intentional removal:

flexkit deploy --allow-breaking-changes

The acknowledgement option does not migrate or delete stored values. It confirms that you understand the field will disappear from Flexkit while its old values remain in the database.

Removing Multiple Attributes

One acknowledgement applies to all entity and attribute removals reported for that deployment. Review every removal in the CLI output before rerunning the command.

Undoing the Local Change

If the removal was accidental, restore the attribute definition with its original dataType and run flexkit deploy again without the acknowledgement option.