Get average time difference between consecutive fields grouping by users

[Brett]

Hi @priyanka2,

The issue seems to be arising from trying to incorporate an aggregated field with a pre-aggregated field as QuickSight does not allow you to handle scenarios like these.
Here are a couple helpful articles that dive deeper into scenarios where mismatched aggregations arise:

Finding solutions for mismatched aggregation errors in QuickSight calculations

Finding solutions for mismatched aggregation errors in QuickSight calculations Mismatched aggregation errors are common QuickSight calculation errors reported by users. This error occurs when the calculated field contains both aggregated and non-aggregated (row-level) values. For users new to QuickSight, it’s not always apparent what causes this error. It is important to understand what is aggregated vs non-aggregated from a QuickSight perspective. This article explores common cases where these …

Level-Aware Calculations: Tips and Best Practices

[Level-Aware Calculations in Amazon QuickSight] Level-Aware Calculations (LAC) are powerful functions that allow us to perform calculations at a granularity level which is different from the granularity of our datasets and/or visuals. The sample dataset referenced by this article is a dataset of product orders placed by customers. Each order can contain multiple products and each product in an order has a unique Line Item ID. Each row of our dataset represents one line item but we want to per…

I’d suggest to review these and see if it helps diagnose your issue; if you have any additional questions, it may be easier to assist further if you’re able to create an anonymized copy of your dataset and upload the analysis to QuickSight Arena so that we can test out various work arounds.