#16055 Query Unexpected Data Point Storage Increase with Calculated Fields

Dear ThingsBoard Support Team,

I am currently testing ThingsBoard Cloud on the Prototype plan and have observed an unexpected increase in Data Point Storage Days after creating a calculated field.

Here is my test setup: Telemetry sent only once in single device. Telemetry Payload sent : { "current" : 1, "voltage" : 220 } Before sending telemetry: 9,060 After sending telemetry: 9,180 After creating a Calculated Field that simply doubles current (current * 2): 10,275 There are no other devices or telemetry in the device profile. Interestingly, when I configure a custom TTL in the Calculated Field, the storage usage behaves as expected. However, when I do not specify a custom TTL, the calculated field appears to increase data point storage usage unexpectedly. Could you please help me understand: Why does the calculated field behave as expected when a custom TTL is specified, but not when the custom TTL is left unset? When no custom TTL is specified for a calculated field, which TTL is applied to its output? How exactly are calculated-field output points counted toward Data Point Storage Days? Is there a way to determine the exact number of data points generated/stored by the calculated field? I have attached screenshots showing the calculated field configuration, the generated new_curr telemetry, and the storage behavior for reference.

Please let me know if you need any additional information, logs, or screenshots from my account.