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.
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.