We would our consumers to utilize the 'Auto active remote task definition' setting for our remote task definition. Through some testing it looks like they enable that, the trigger gets removed when a new version is published. Is there any way to retain the trigger condition?
When a revision of a remote task definition is created it creates a new remote task definition. The trigger in the consumer instance is not carried over to the new revision when synced. This will be corrected on the next release of Service Bridge. For now we recommend not auto activating so that the correct configurations can be made before activating.
