---
title: "Comala Publishing Cloud is creating duplicate pages in the target space"
canonical: "https://support.appfire.com/space/SUPPORT/2049638466/Comala%20Publishing%20Cloud%20is%20creating%20duplicate%20pages%20in%20the%20target%20space"
format: markdown
---
## \uD83E\uDD14 Problem

There are duplicated pages in the target space:

![image_2025-05-21_101755821.png](media://26bda7bd-deea-46ff-9692-365d908ca681)

This issue typically arises when the workflow established in the source space includes a trigger that activates the [publish-page macro](https://appfire.atlassian.net/wiki/spaces/CDMC/pages/2193950517) upon reaching the [final state of the workflow](https://appfire.atlassian.net/wiki/spaces/CDMC/pages/657398965). It's important to note that the publishing task is already being executed in the background by Comala Publishing, as detailed in: [https://appfire.atlassian.net/wiki/spaces/CPCL/pages/646807871](https://appfire.atlassian.net/wiki/spaces/CPCL/pages/646807871). In summary, the problem is occurring because the publishing task is being initiated twice.

## \uD83C\uDF31 Solution

Please follow the steps below to address this behavior:

1. Navigate to the source space and select **Space settings**.
2. Locate **Comala Document Management** and open the applied workflow using the code editor.
3. Scroll down to the triggers section and find the one that includes the publish-page macro.
4. Remove the highlighted trigger and save the changes
5. Delete the duplicated page from the target space:
6. Go to the issued page in the source space and open the [Page Analysis diagnostic tool](https://appfire.atlassian.net/wiki/spaces/CPCL/pages/953516116):
7. In the Overview tab it can be seen which page from the target space is currently linked with the source space page:
  In this case it’s linked with the duplicated page we deleted, which is not the expected one.
8. To fix this, go to the Diagnostics tab and click on ‘Link it to this page’:
9. Now the expected page is displayed as Target Page in the Overview tab:
10. Once this issue is resolved, please rerun the workflow process until it reaches the final state again, and confirm that the problem no longer occurs.