IntegrationHub - Flow, Sub-flow, and Actions deactivated after plugin upgradeIssue After the IntegrationHub plugin upgrade, some actions/flows/sub-flows started showing as deactivated (active = false).ReleaseAll releasesCauseAfter the IntegrationHub plugin upgrade, if an action, flow, or subflow is deactivated (active = false), it means you cannot add it to new flows using the action picker in Flow Designer in the future, and it is deprecated. However, for existing flows where the action was added before the deprecation, it will continue to function.ResolutionSetting "Active" to false does not mean the action will stop working; it simply means the action will no longer be available in the action picker for new flows. This ensures that customers use the latest actions instead of deprecated ones in new flows. It is up to the customer (for custom flows) and the team managing the flows/subflows (OOB flows) to decide whether they want to update their subflow/flow with the latest action or continue using the same flow with a deprecated action.