Issues Deleting Connections and Integrations in Celigo – Possible Bugs & Feature Requests

Hi all,

While cleaning up our Production environment, I ran into several issues that seem like bugs or unexpected behavior in Celigo:

  • After deleting all flows, imports, exports, and integrations, I still can’t delete certain connections. The UI says there’s still an alias referencing them.
  • I tried restoring the integration to manually remove the alias, but got the following error:
    “The target resource must be attached to a connection that is registered to the same integration.”
  • I then attempted to restore some import steps from the integration (note: I had purged some others connected to the integration earlier), but now I can’t restore the integration at all. It gives this error:
    “This document is referenced by a flow.”

So I’m stuck:

  • The original integration, flows, and steps are deleted (in the Recycle Bin, and some purged).
  • I can’t restore the integration.
  • I can’t delete the connection.
  • I now have a few restored import steps that are also undeletable it will then say : "This import is referenced by the resources below. Only resources that have no references can be deleted."

In addition, it would really help if:

  • Just like the cleanup I/O tool there would be a possibility to clean up the integration simply by a button which then also gives the user the choice to keep certain stuff or to completely delete the integration with its dependencies.
  • We could select and delete multiple imports/exports/flows at once,
  • There was a way to purge the entire recycle bin or multi-select items to delete in bulk.

I’ll create a support ticket to request a reset of my environment. But ideally, admins should be able to fully reset an environment themselves—especially in these situations where references get stuck.

Lastly, I noticed:

  • I can create multiple environments, but only enable a maximum per license.
  • However, I cannot delete disabled environments. Would be useful to allow that as well.
1 Like

Given that other environments are truly additional accounts, the deletion mechanism for it is/was trickier so we opted to defer that to a later time. Is there any particular reason you need to delete an environment as opposed to just disabling it or you just noticed you couldn’t?

If you delete what you can, then purge those resources, do you still have the issue?

Hi Tyler,

Yes, the issue is that I can't fully purge the flows/integration in the existing environment.

I deleted everything, but one connection — “integrator.io” — couldn’t be removed. It reported that an alias still existed, likely one created by the “Clean I/O Tool” I had previously used.

To remove the alias, I attempted to restore the “Clean I/O Tool” integration. However, the restoration failed. It seems I first need to restore the related flow steps — but I no longer have all of them. I tried restoring a few, but now I’m stuck: I can’t delete the restored flows, and I also can’t fully restore the integration.

I’ve already contacted support, but they said they’re not allowed to reset the environment due to liability reasons. Still, this environment wasn’t heavily used, and a full reset is needed.

Let me know if there’s any way we can escalate this or get approval to wipe the environment

We don’t have anything for wiping environments. We can for sure take a look at what can’t be deleted as that would be a bug.

Hi,

Thanks! I’m currently in contact with Celigo Support — great to see they picked it up so quickly.

@normanlibres and I are discussing offline :slight_smile:

1 Like

Thanks Tyler and @normanlibres !