​@Haru how exactly are you triggering it? Could you share some more details so we can try to help?

​@Gustavo Boregio 

Could you please check Action #1 in our automation. I see it’s set to Clear User Field right after the external request and before the next steps. This means the custom field should be cleared once the previous action completes.

.

If it’s still not triggering, please verify that the trigger condition for the custom field change is set correctly (e.g., "has changed to any value") and that the field is actually being updated in the chat flow.

.

Let me know if you want me to take a closer look!

We’ve encountered another issue: after the chat status is changed from Open to Closed (Move ‘open’ to ‘close’), the messages that we want to capture and send externally (via external request) are not being picked up by the action system we set up.

.

Could you please check this? It’s affecting the overall workflow

Hey ​@Haru, I'm not sure what you're trying to do, but your setup seems prone to having issues.

To check this, I suggest you double check the sequence of events and what triggers when. Having empty data collection blocks triggered by a tag being added is probably not the safest way to accomplish what you're trying to accomplish.

If you'd like I'd be happy to jump on a troubleshooting call to help you debug your automation - you can book them at gusboregio.com 

Hi ​@Gustavo Boregio 

For the issue with Clear User Field, I will double-check the sequence and rules again to make sure everything is set correctly.

Regarding the chat being changed from Open to Closed (Move ‘open’ to ‘close’), it seems we’ve found the problem—there is a rule that automatically closes the chat.

Also, could you please let me know if there is any additional cost for the troubleshooting video call?

Thanks again for your help!

Hey ​@Haru happy to hear you're making progress!

Yes, these calls are paid, you can book them on this link.

Hi ​@Haru did you get to solve your issue?