# Deck upstream with tags

**URL:** <https://discuss.konghq.com/t/deck-upstream-with-tags/10591>\
**Category:** General\
**Tags:** kong-gateway\
**Created:** [August 29, 2022, 9:29am UTC](https://discuss.konghq.com/t/deck-upstream-with-tags/10591 "2022-08-29T09:29:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MartijnJansen](https://avatars.discourse-cdn.com/v4/letter/m/e9c0ed/32.png) [@MartijnJansen](https://discuss.konghq.com/u/MartijnJansen)\
**Post date:** [August 29, 2022, 9:29am UTC](https://discuss.konghq.com/t/deck-upstream-with-tags/10591/1 "2022-08-29T09:29:03Z")

</div>

During testing with Konnect and Deck the following error scenario has occured:

Updating a service on Konnect with deck results in an error in combination with upstreams and tags.

{  
“code”: 9,  
“message”: “listing resources scoped to a resource while applying a filter are not yet supported”  
}

The call deck struggles with is: [https://us.api.konghq.com/konnect-api/api/runtime\_groups/](https://us.api.konghq.com/konnect-api/api/runtime_groups/)/upstreams/d5d0e5ee-4d83-4125-9b26-6b15344e084d/targets?size=1000&tags=openapi-httpbin.yaml

When testing the same scenario with a local kong gateway (running the latest docker version) there is no problem updating the service with deck. We’ve tested the same call above (/upstreams?tags=tagid) which returns the expected upstream. Any idea what might cause this problem?

---

<div class="post-metadata">

**Author:** ![Jerome\_Guillaume](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/jerome_guillaume/32/3348_2.png) [@Jerome\_Guillaume](https://discuss.konghq.com/u/Jerome_Guillaume)\
**Post date:** [September 5, 2022, 8:22am UTC](https://discuss.konghq.com/t/deck-upstream-with-tags/10591/2 "2022-09-05T08:22:30Z")

</div>

Hello,

Unfortunately this is a known limitation and we are working to improve this tag mechanism with decK.