Exciting news - Release 303 is here!
The Tulip team has rolled out some fresh updates across multiple features, along with some bug fixes. Check out the release notes and dive into what’s new.
Share your thoughts and questions below 
1 Like
Hi @jakerigos – Referring to the updated feature: “Connector functions can now only be archived if they are not used by any apps or automations,” I have a couple of questions:
- If a connector is used in an archived application, will it still be possible to archive the connector function?
- If a connector is used in an old version of an application, will it be possible to archive it? For example, if the application is currently running Version 3 but Version 1 of the application uses the connector I want to archive, what happens in this scenario?
Thanks in advance for your help!
2 Likes
Hey @nicolettenaya and @thorsten.langner,
- If a connector is used in an archived application, its connector functions cannot be archived.
- If a connector is used in an older version of an application, you can archive it. In this case, the older versions of the application will continue using a snapshot of the archived connector.
Let me know if this answers your questions!
1 Like
Thank you for the answer…
So…
…how can I ever tidy up my tons of connector functions then? Do I always have to publish a dummy version of an app with no connectors before archiving an App? That feels not good to me…
That makes totaly sense to me and should be considered for archived apps as well…
1 Like
Following up on Thorsten’s question above on archived apps
Hey all,
Appreciate the patience here! The behavior for the first point is actually:
- If a connector is used in an archived application, its connector functions can be archived.
If it can’t be archived, it’s likely a bug. This should be the case now—hope this clarifies!
3 Likes