Hi Dan, the problem here is that when the sequence is triggered by your webhook, it changes a variable which then triggers another sequence. After that sequence runs, it creates a second entry in the log for the first sequence.

I can see that it's not actually executing twice, just that it's logging a second time. I will need to fix this but it will take a couple of days. I'll post back here once it's resolved.

Is this a caveat of the system, or are there any amendments I can make to the sequences to stop this from happening?

No, nothing you need to do differently, it's a bug in the way sequences are logged which I wasn't aware of until you raised it here. I'll be fixing this in the next couple of days.

Hi Dan, this is now fixed. It won't change previous log entries, but going forward you shouldn't see this issue occuring.

Excellent, I'll check next time I leave the house.

All good now, just need to tweak my geofence on my home location so I don't trigger multiple arrival/leave requests when I venture out on foot.I have experimented with a 'too_soon' variable but not fully happy with the results just yet.

Great, glad the logging is working. That's a tricky problem to solve - interested to hear the solution you come up with!