If you are getting the alert "this workflow has already been applied to this trip" when attempting to add an Automations Workflow to a trip, you likely have automations on that trip that are also in the workflow you are attempting to apply. Tern will not let you add the same automation to a trip twice.
This is expected behavior so that you don't have multiple automations doing the same thing.
Any automations that are in the workflow that are already on this trip, you will need to delete from the trip. This way when you add the workflow, it won't flag that you are adding some automations twice.
If you confirm that there are no duplicate automations on the trip, and your workflow will still not apply, please reach out to Tern customer support at [email protected]
Why a workflow you applied isn't on the Workflows tab
A trip's Workflows tab lists only workflows owned by the trip owner. Any other workflow still applies its tasks and automations to the trip, but it does not get a row on the tab.
That covers two cases:
You applied a workflow from Shared with me or Tern Community to your own trip.
You are a collaborator, and you applied a workflow from your own library to someone else's trip.
If a collaborator applies a workflow owned by the trip owner, it does appear on the tab.
Because these workflows have no row on the tab, the "This workflow has already been applied to this trip" alert does not fire for them. Applying one twice stacks duplicate automations.
Removing duplicates from a workflow with no row
Go to the trip's Automations tab and delete each duplicate automation. This stops future emails from those automations.
Go to the trip's Tasks tab and delete the duplicate tasks.
To confirm what was applied and when, go to the trip's Activity tab.
This works on both web and mobile. If you can't locate the duplicates or they reappear, email [email protected] and we'll clear them for you.