Condition block - Save Button Disabled _reg

Hello Jayakumar,

Thanks for reaching out, and I'm sorry for the trouble with the Condition block.

When you set Condition On as User Message and choose Equal or Contains, the Save button is disabled because a comparison value is still required. Equal and Contains need a value to compare against (the text or number to match), so until that field is filled in, the configuration is incomplete and Save stays disabled. Exists does not require a comparison value, which is why Save is enabled in that case.

Please do the following:

1. In the Condition block, after selecting Equal or Contains, make sure you enter the value you want to compare the user message against.
2. Confirm no other required fields in the block are left empty.
3. Then try saving again.

Also, if your Condition Node is connected directly to the Trigger Node, note that a check on the user's reply can evaluate incorrectly, because the flow runs the instant the message is delivered before the customer has replied. If that applies to your setup, add a SetDelay Node between the Trigger and the Condition Node so the system waits for a reply before evaluating.

If the Save button remains disabled after entering the comparison value, please share your registered Pabbly account email, the specific flow where this occurs, and a short screen recording of the behavior so our technical team can investigate further.

Hello,

Just following up on our previous email to check if you need any further assistance from our end.

Please feel free to let us know if you have any questions or concerns. We’ll be happy to assist you.

Hello,

Just following up on our previous email to check if you need any further assistance from our end.

Please feel free to let us know if you have any questions or concerns. We’ll be happy to assist you.