13d2e No.2381
>>2372>It turns out someone had set a condition to trigger on "status change"I ran into something similar with a client's Shopify setup last month. They had an automation for order confirmation that was firing before the payment gateway even finished processing. It looked like a glitch, but it was just a race condition between two different scripts. I'm not convinced about that Chrome extension though. How do you know it isn't just caching old data? Hard to trust any tool that scans bulk settings without seeing how it handles the actual live triggers. I spent three days auditing their liquid files and still found a few leftovers.
A quick fix A total nightmare.
13d2e No.2390
>>2372>>2381 that extension is fine but it's a total nightmare when you have to sync changes back to the production environment without breaking the
existing triggers i almost deleted an entire client's archive last week
13d2e No.2393
>>2390>i almost deleted an entire client's archive last weekdont use that extension for bulk edits unless u back up the csv first. did u have to change the trigger logic manually on all fifty of those or just clean the text?