| The CLI reports a missing required value | Supply --api-key, --destination, and --connection, or set their corresponding environment variables. Configuration must also be available when creating a connection. |
| The connection name is rejected | Use only lowercase letters, numbers, and underscores, and begin with a lowercase letter or underscore. |
| An automated redeployment does not update the connection | --non-interactive accepts the default answer, which is normally No for overwriting. Use --yes for an intentional update. |
| Production configuration changed unexpectedly | A redeployment supplied a non-empty configuration file. Restore the correct values and omit configuration from future code-only deployments. |
| A dependency fails to install | Confirm the dependency is declared in the project root, supports the selected Python version and Linux amd64, and is available from the configured package index. If both dependency files exist, remember that pyproject.toml takes precedence. |
| The connector reaches the source locally but not after deployment | Configure source allowlists or the required SSH, VPN, private-link, or Hybrid connectivity. Check the cloud and region associated with the destination. |
| The connector is deployed but no sync runs | New connections are paused. Enable the connection or start the initial sync from the dashboard or REST API. |
| New code is not used by the current sync | A sync already in progress finishes with the old code. The next sync uses the newly deployed code. |
| Destination names differ from source names | Confirm the naming strategy and Fivetran renaming rules. The strategy cannot be changed by redeploying an existing connection. |
| The connector is terminated during a large sync | The SaaS production runtime has 4 GB of RAM. Stream or batch data, reduce concurrency, avoid fetchall(), and checkpoint between manageable batches. |
| Existing rows do not contain a newly added field | Redeployment changes future processing but does not automatically backfill historical rows. Run a historical re-sync if the source can reproduce the data. |
| Rows duplicate after a primary-key or inferred-schema change | Correct the schema, drop the affected destination table when required, and perform a historical re-sync. |
