# Using Aggregations in Create Record Logic

**URL:** <https://community.tulip.co/t/using-aggregations-in-create-record-logic/15756>\
**Category:** General\
**Created:** [October 23, 2025, 2:01pm UTC](https://community.tulip.co/t/using-aggregations-in-create-record-logic/15756 "2025-10-23T14:01:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![danielpomeranz](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/danielpomeranz/32/9379_2.png) [@danielpomeranz](https://community.tulip.co/u/danielpomeranz)\
**Post date:** [October 23, 2025, 2:01pm UTC](https://community.tulip.co/t/using-aggregations-in-create-record-logic/15756/1 "2025-10-23T14:01:00Z")

</div>

I am not sure if I would call this a bug, but I was surprised, so I thought I would share this behavior here for posterity’s sake.

If you use aggregations in a “chunk” of create and store triggers. The aggregation will not re-calculate for the second use.

In the example below, the create record (red) should hypothetically increment the count aggregation so that the green one will have a larger number. But the way Tulip bundles these triggers this does not seem true.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/2/23b1d937722363798483959dfcf3ee5cc7e12da3.png)

This is inconsistent with how Tulip handles aggregations elsewhere… but I also understand that changing the behavior could be bad for a lot of people. So just an FYI.