After you deploy a replication job, you cannot edit or add tables to
it. Instead, add the tables to a new or duplicate replication job.

## Option 1: Create a new replication job

Adding tables to a new job is the simplest approach. It prevents historical
reloading of all the tables and prevents data inconsistency issues.

The drawbacks are the increased overhead of managing multiple
replication jobs and the consumption of more compute resources, as
each job runs on a separate ephemeral Managed Service for Apache Spark cluster by
default. The latter can be mitigated to some extent by using a shared static
Managed Service for Apache Spark cluster for both jobs.

For more information about creating new jobs, see the
[Replication tutorials](https://docs.cloud.google.com/data-fusion/docs/how-to/using-replication).

For more information about using static Managed Service for Apache Spark cluster in
Cloud Data Fusion, see
[Run a pipeline against an existing Managed Service for Apache Spark cluster](https://docs.cloud.google.com/data-fusion/docs/how-to/running-against-existing-dataproc)

## Option 2: Stop the current replication job and create a duplicate

If you duplicate the replication job to add the tables, consider the
following:

- Enabling the snapshot for the duplicate job results in the historical load of
  all the tables from scratch. This is recommended if you cannot use the
  previous option, where you run separate jobs.

- Disabling the snapshot to prevent the historical load can result in data
  loss, as there could be missed events between when the old pipeline stops and
  the new one starts. Creating an overlap to mitigate this issue isn't
  recommended, as it can also result in data loss---historical data for the new
  tables isn't replicated.

To create a duplicate replication job, follow these steps:

1. Stop the existing pipeline.

2. From the Replication jobs page, locate the job that you want to duplicate,
   click and
   **Duplicate**.

3. Enable the snapshot:

   1. Go to **Configure source**.
   2. In the **Replicate existing data** field, select **Yes**.
4. Add tables in the **Select tables and transformations** window and follow the
   wizard to deploy the replication pipeline.

> [!NOTE]
> **Note:** If you run a duplicate replication job against the same target BigQuery dataset as the original job, don't run the original job again, as it can cause data inconsistency.

## What's next

- Learn more about [Replication](https://docs.cloud.google.com/data-fusion/docs/concepts/replication).