Steps to reproduce:
- Add a Tag to any product.
- Open the Product Picker from AppBridge
- Click
Add filter +→Tags - You may notice that the newly added tag is not present in the list.
- It takes perhaps a few minutes for the Tag to show up there.
Steps to reproduce:
Add filter + → TagsHey @flavio-b, thanks for flagging as always, just confirming, is this using the resource picker API via the new CDN method?
Want to make sure I’m replicating this correctly!
Hi Alan, yes it’s the resource picker from the CDN AppBridge, of type product.
Hey @flavio-b - thanks for confirming that. I’m going to try and repro this on my end as well, but just a couple quick questions first: roughly how long does it take before the new tag shows up in the picker? If you type the exact tag name into the Tags filter, does it appear then, or is it missing entirely until later? Also, does closing/reopening the picker or refreshing the page make any difference, and have you seen the same behaviour on a fresh dev store too, or just on this store?
Just wanted to see if I can narrow down reproduction behaviour here - hope to hear from you soon!
Hi Alan,
In my test, it took probably around 5 minutes for the new tag to show, and I only added 1 tag. I did enter the exact tag name in the search, and did refresh the page a few times.
The sync time in isolation might not look too bad, but I think the problem is it breaks the expectation compared to other tasks the merchant does: When they enter a new product, it shows up immediately in the picker, but for tags, this delay gives the impression that something is broken, or that the merchant did something wrong.
Hey @flavio-b - quick follow-up here.
I’ve put together a small repro on my side using the CDN App Bridge product picker with type product, just to make sure we’re testing something close to your setup.
At a code level, my flow right now is:
shopify.resourcePicker(…) using the product picker pathWhat I’m seeing so far is:
So this does seem directionally similar on our end, but I just want to make sure we’re comparing correctly
If you’re able to share the exact resourcePicker invocation/options you’re using, plus the small part of the flow where the product tag is being added, that would be really helpful. Also, are you reopening the picker fresh each time, or
keeping the same picker/session open?
No need for the full app or anything large, just the relevant snippet if that’s easier. Hope to hear from you soon!
Hi Alan,
Yes, you’ve got it. In my example, I added the tag to a product using the Shopify Admin interface, not GraphQL, but it’s the same result you noticed: The tag doesn’t show up in the Product Picker for a period of time.
Yes, I did refresh the page several times to ensure the resource picker is fresh, before doing each new test.
Here’s a portion of the front-end code:
const selected = await shopify.resourcePicker({
type: 'product',
action: 'select',
multiple: true,
filter: {
variants: true,
hidden: true,
draft: true,
archived: true
}
});
Thanks, @flavio-b - looking into this internally, definitely does seem like odd behaviour.
Hey @flavio-b , looping back here, appreciate the patience while I dug into this one as always.
So, just to confirm, what you’re seeing is actually expected platform behaviour at the moment. Without sharing too much internal detail, what I can say is that currently, the picker’s tag filter list draws from a tag index that has a short propagation delay after new tags are added. The product record itself updates immediately (which is why you see the tag right away via the Admin/API), but the tag filter path inside the picker has its own eventual consistency window, which is what’s causing that lag.
Unfortunately there’s no parameter in the resourcePicker invocation today that forces this, so there’s not a workaround we can currently suggest
That said, it’s a valid point about the UX inconsistency. The fact that products appear instantly in the picker but tags don’t does create a confusing experience for merchants for sure, so I’m flagging that gap internally. I can’t promise a timeline on any changes, but it’s definitely worth tracking and I’m happy to advocate for changes on my end here.
Hi @Alan_G, thanks for flagging this internally. Hopefully an update will be implemented to reduce the delay, at some point.