# Separate transaction for every resolver in AWS Lambda

**URL:** <https://discuss.elastic.co/t/separate-transaction-for-every-resolver-in-aws-lambda/369688>\
**Category:** APM\
**Tags:** nodejs, aws-lambda\
**Created:** [October 28, 2024, 4:54pm UTC](https://discuss.elastic.co/t/separate-transaction-for-every-resolver-in-aws-lambda/369688 "2024-10-28T16:54:09Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![mkaniaa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mkaniaa/32/138787_2.png) [@mkaniaa](https://discuss.elastic.co/u/mkaniaa)\
**Post date:** [November 9, 2024, 4:28pm UTC](https://discuss.elastic.co/t/separate-transaction-for-every-resolver-in-aws-lambda/369688/8 "2024-11-09T16:28:49Z")

</div>

I created a separate topic for the `maxLength` JSON issue: [Max Characters Length for JSON in transaction labels](https://discuss.elastic.co/t/max-characters-length-for-json-in-transaction-labels/370257).

The problem described here is solved and this topic can be closed.

---

_[View the full topic](https://discuss.elastic.co/t/separate-transaction-for-every-resolver-in-aws-lambda/369688)._