You can use ContinueAsNew to avoid the history size limit issue. Can still potentially Signal the Workflow doing the aggregation from other Workflows and periodically call ContinueAsNew to prevent a large history. Here is an example of how to use ContinueAsNew.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Scale Temporal workflow | 11 | 365 | January 5, 2026 | |
| Using temporal for scalability within an activity | 7 | 1190 | May 24, 2023 | |
| Creating 10m+ workflows Best Practices | 3 | 540 | October 3, 2024 | |
| Best way to streaming data between activities in Temporal | 6 | 2588 | August 2, 2024 | |
| Validation of app architecture using temporal | 10 | 1525 | October 18, 2021 |