# Feature request query activity input but not pull consume from queue

**URL:** <https://community.temporal.io/t/feature-request-query-activity-input-but-not-pull-consume-from-queue/5374>\
**Category:** Community Support\
**Tags:** general-impl\
**Created:** [July 19, 2022, 2:43am UTC](https://community.temporal.io/t/feature-request-query-activity-input-but-not-pull-consume-from-queue/5374 "2022-07-19T02:43:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![beta\_alpha](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/beta_alpha/32/1638_2.png) [@beta\_alpha](https://community.temporal.io/u/beta_alpha)\
**Post date:** [July 19, 2022, 2:43am UTC](https://community.temporal.io/t/feature-request-query-activity-input-but-not-pull-consume-from-queue/5374/1 "2022-07-19T02:43:49Z")

</div>

Worker resouce may be related with task input, for not always assume using maximum resource (in k8s).  
Given the ability query activity input from queue then apply resource estimate algorithm for worker may help a lot.

---

<div class="post-metadata">

**Author:** ![tihomir](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tihomir/32/6580_2.png) [@tihomir](https://community.temporal.io/u/tihomir)\
**Post date:** [July 19, 2022, 6:06pm UTC](https://community.temporal.io/t/feature-request-query-activity-input-but-not-pull-consume-from-queue/5374/2 "2022-07-19T18:06:58Z")

</div>

Thanks for the input.

Wanted to ask why do you need to read the activity input from task queues?  
If I understand question correctly, you could in test run those estimate algorithms with your test data inputs and default/custom data converter.

Another way could be to use the [sessions api](https://docs.temporal.io/concepts/what-is-task-routing/#sessions) and have two activities assured to be running on same worker. One activity would be responsible for running the estimations and the other one would be your run activity.

---

<div class="post-metadata">

**Author:** ![beta\_alpha](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/beta_alpha/32/1638_2.png) [@beta\_alpha](https://community.temporal.io/u/beta_alpha)\
**Post date:** [July 20, 2022, 3:09am UTC](https://community.temporal.io/t/feature-request-query-activity-input-but-not-pull-consume-from-queue/5374/3 "2022-07-20T03:09:05Z")

</div>

Thanks for your reply.

We are using workflow process mess data, the data size depends on the input given location which means that the need resources always be dynamic.

I will try your second suggestion (run the estimations but submit k8s job task with estimated resources).