How Remove Tag workflows work
When a comment matches a Remove Tag workflow:
The selected tag is removed if it exists.
The tag is blocked from being added again while the comment still matches the workflow.
Removal takes priority over Add Tag workflows targeting the same tag.
This prevents workflow loops where one rule adds a tag and another removes it repeatedly.
Removal takes priority
If an Add Tag workflow and a Remove Tag workflow both match the same comment, the Remove Tag workflow wins.
The tag should not be added temporarily or trigger downstream workflows before being removed.
Example
A comment matches both workflows:
An Add Tag workflow adds
Escalation.A Remove Tag workflow removes
Escalation.
The final result is:
Escalationis not applied.Workflows that depend on
Escalationdo not trigger.The tag remains blocked while the Remove Tag workflow still applies.
đ Note: The block applies to the specific comment, tag, and removal workflow combination.
When the tag can be added again
The tag block is cleared when the removal rule no longer applies.
This includes when:
The comment no longer matches the workflow conditions.
The Remove Tag workflow is disabled.
The Remove Tag workflow is deleted.
The workflow conditions change and the comment no longer qualifies.
The tag is removed from the workflow configuration.
Once the block is cleared, another workflow can add the tag again.
Recommended use cases
Use Remove Tag workflows to:
Remove outdated routing or status tags.
Prevent conflicting automation rules.
Clear tags when comments no longer meet escalation criteria.
Keep reporting and workflow triggers aligned with current comment conditions.
đĄ Tip: Review Add Tag and Remove Tag workflows together when they target the same tag. Conflicting conditions can create unexpected routing or reporting results.