# Issues that prevent data generation The following issues prevent a data generation or subsetting job. ## Structural and workspace access or permissions

Issue	Description	How to resolve
Structural license expired	The current Structural license is expired.	Update the Structural license key.
No workspace configured	The Structural instance does not have any workspaces to generate data from.	Create and configure a workspace.
Insufficient workspace permissions	You do not have permission to run data generation on this workspace.	Request access from the workspace owner or a user who has permission to manage workspace access.

## Source and destination data availability

Issue	Description	How to resolve
Unable to connect to the source database	The source database connection is either missing or incomplete. If the connection uses a secret from a secrets manager, the secret is not available. For example, the authentication details might be incorrect, or the secret might not be in a valid format.	Edit the workspace configuration to complete the source database connection. For a secret from a secrets manager, verify the secrets manager configuration and the secret format. Make sure to test the connection.
Unable to connect to the destination database	The destination database connection is either missing or incomplete. If the connection uses a secret from a secrets manager, the secret is not available. For example, the authentication details might be incorrect, or the secret might not be in a valid format.	Edit the workspace configuration to complete the destination database connection. For a secret from a secrets manager, verify the secrets manager configuration and the secret format. Make sure to test the connection.
Only for licenses that have a configured size limit - The source database size exceeds the maximum allowed	Only applies to licenses that are configured to enforce a maximum data size. When a Structural license is configured with a maximum source database size, then if the source database is larger than that maximum, the generation fails.	Reduce the size of the source database.

## Table mode and generator configuration

Issue	Description	How to resolve
Preserve Destination - cannot resolve foreign key references	A table that uses Preserve Destination mode is referenced from another table.	Change the table mode for this table to De-Identify. OR Change the table mode of the other table to Preserve Destination.
Truncate - cannot resolve foreign key references	A table that uses Truncate mode is referenced from another table.	Change the table mode for this table to De-Identify. OR Change the table of the other table to Truncate.
Cross Table Sum - incomplete generation	A column is assigned the Cross Table Sum generator, but some required configuration field values are missing.	Update the generator configuration to provide the missing values.
Incremental mode - circular foreign key dependency	There is a circular foreign key dependency between tables that use Incremental mode.	Change the table mode for at least one table to De-Identify

## Schema changes

Issue	Description	How to resolve
Unresolved schema changes	There are detected schema changes that are not resolved, and the workspace is configured to block data generation on those schema changes.	Go to Schema Changes to identify and resolve the changes.

## Subsetting configuration The following errors occur when you attempt to generate a subset. They do not apply if **Use subsetting** is turned off.

Issue	Description	How to resolve
No target tables configured	The subsetting configuration does not include any target tables.	Add at least one target table to the subsetting configuration.
Invalid target table configuration	A target table has an invalid percentage value or `WHERE` clause.	Update the subsetting configuration to correct the target table percentage or where clause.
In-subset table uses Truncate mode.	A table that is in the subset uses Truncate table mode.	Change the table mode to De-Identify.
In-subset table uses Preserve Destination mode.	A table that is in the subset uses Preserve Destination table mode.	Change the table mode to De-Identify.
In-subset table uses Incremental mode.	A table that is in the subset uses Incremental table mode.	Change the table mode to De-Identify.

## Upsert issues When upsert is enabled, the following issues cause the upsert job to fail.

Issue	Description	How to resolve
Destination database not populated	The destination database is empty.	Update the workspace to disable upsert, then run a regular data generation job to populate the destination database. You can then re-enable upsert.
Invalid table mode	A table is assigned a mode other than De-Identify or Truncate.	Change the table mode to De-Identify or Truncate.
Unable to connect to the intermediate database	The intermediate database connection is either missing or incomplete.	Edit the workspace configuration to complete the intermediate database connection.
Unresolved schema conflicts	There are schema conflicts between the source and destination databases.	Update the source or destination database schema to resolve the changes.

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.tonic.ai/app/workflows/data-generation-run-job/data-generation-issues.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.