feat(automations): narrow condition options for delayed rules instead of warning

When a delay is on, the condition attribute dropdown for conversation-level events
offers only Status, and attribute_changed is dropped from the operator list for any
delayed rule. Toggling the delay on resets conditions the delayed rule can't use.
This makes unsupported delayed rules unconstructable, so the inline restriction
warning (and its i18n strings) are removed.
This commit is contained in:
Tanmay Deep Sharma
2026-07-15 18:35:11 +05:30
parent be381b940d
commit 852a219e0b
2 changed files with 16 additions and 23 deletions
@@ -38,11 +38,7 @@
"DAYS": "Days"
},
"ERROR": "Delay must be between 10 minutes and 30 days",
"HELP_TEXT": "Delayed rules run only if the conditions still hold when the delay ends, and apply to conversations with activity after the rule is created.",
"RESTRICTED": {
"ATTRIBUTE_CHANGED": "A delay can't be used with an \"attribute changed\" condition, because the change can't be re-checked when the delay ends.",
"CONVERSATION_NON_STATUS": "For conversation events, a delay is only available when every condition uses the Status attribute."
}
"HELP_TEXT": "Delayed rules run only if the conditions still hold when the delay ends, and apply to conversations with activity after the rule is created."
},
"CONDITIONS": {
"LABEL": "Conditions"