Disable support for multiple action packs for a datasource instance
Starting November 19, 2025, Glean will no longer allow creating multiple action packs for the same datasource. This change ensures a simpler, more reliable setup and enablement experience.
What’s changing
- Glean will no longer allow creation of multiple action packs for the same datasource instance.
What remains the same
- You can still enable multiple action packs for different datasource instances. For example, if you have two datasource instances for Jira, you can enable two different action packs.
- You can still create multiple action packs for Databricks, Snowflake as long as the configuration (Databricks: HostUrl, SpaceId, WareHouseID; Snowflake: Account Identifier) of the two packs is not identical.
When it’s happening
- This change will come into effect on November 19, 2025.
What we need from you
If you have duplicate action packs for the same datasource instance:
- Delete one of the duplicates.
- If you don’t delete a duplicate, actions will continue to run, but you won’t be able to edit either pack until one is removed. When deleting, you can identify any agents using the pack you’re removing and update those agents to point to the retained action pack.
No action is needed if you don’t have multiple action packs for the same datasource instance.