Wanted to flag a cart.transform.run issue that started recently with no change on our side.
Our function returns a linesMerge operation to merge a few tagged cart lines under a wrapper parent variant (the standard bundle pattern). The function executes successfully and returns a valid linesMerge every run, but the merge is never applied: the cart and checkout keep showing the original component lines, un-merged.
It worked fine until ~2026-06-18, then stopped with no deploy or code change. Re-deploying the unchanged function doesn’t help, and it reproduces on both our dev and production apps.
Happy to share function-run logs, operation output, parent variant setup, etc. if that helps, just let me know what’s useful. Thanks!
Hey @shaheem - thanks for flagging this, and for the detail in the writeup.
I did some digging here and what you’re describing appears to line up with a recent change on our end in how a bundle’s parent variant publication is resolved on the merge path.
To confirm, could you share a couple cart tokens from a cart that shows the un-merged lines? This should help us trace the run in our logs. If you could also share the parent/wrapper variant ID and one of the component variant IDs that could also help point us in the right direction.
Thanks!
Hi @shaheem just wondering if you’re still experiencing this. If so, please let me know and share a couple cart tokens from cart’s showing un-merged lines and I can look into this further.
If not, I’ll mark this thread as resolved.
Thanks!