Hi All and Amplitude Team!
I’ve been having an issue where the cohort that I wanted to create keeps not getting computed. The cohort do have a lot of line condition but I was wondering if there are any limitations or ways that I can do to help compute the cohort.
Below is the screenshot of the data that has not computed. It usually happens when I want to substract a certain cohort.
Best answer by Thao Nguyen
Hi
After taking a closer look, we found that the cohort [New] Referral (Retention + Refer Someone) is built based on the cohort [New] Revenue (Transaction > 1, diff verical), specifically it includes users from [New] Revenue (Transaction > 1, diff verical).
Therefore, you can’t add the second clause “not part of cohort [New] Referral (Retention + Refer Someone)” because these two cohorts conflict, resulting in the save failed and returned 0 users. If you chose a different cohort for the second clause that doesn’t have clashing conditions, it will still work.
I understand that the preview says more than 75,000 users who match the condition. Our Engineer advised that the preview runs a temporary computation of the cohort size when you make a change. However, it doesn’t run a thorough check for the definition until you hit Save. In this case, it errored out during the saving process.
Hope this helps! Let me know if you have any questions.
Best regards,
Thao
+9Hi
Do you mind re-creating the cohort and monitoring if it is complete? If not, I will escalate it to our Engineering team to investigate if needed.
Thank you!
Best regards,
Thao
Hi
This error for not able to save the update to a cohort has happened to me a couple of times too.
Another thing is that, while waiting for saving I found the new cohort [Fix] Revenue that I wanted to save in my Cohort List. However, it couldn’t compute and eventually showed 0 user.
If I could get an insight and help regarding this, Thank you!
Hi
Apologies for the inconvenience!
Best regards,
Thao
Hi
After taking a closer look, we found that the cohort [New] Referral (Retention + Refer Someone) is built based on the cohort [New] Revenue (Transaction > 1, diff verical), specifically it includes users from [New] Revenue (Transaction > 1, diff verical).
Therefore, you can’t add the second clause “not part of cohort [New] Referral (Retention + Refer Someone)” because these two cohorts conflict, resulting in the save failed and returned 0 users. If you chose a different cohort for the second clause that doesn’t have clashing conditions, it will still work.
I understand that the preview says more than 75,000 users who match the condition. Our Engineer advised that the preview runs a temporary computation of the cohort size when you make a change. However, it doesn’t run a thorough check for the definition until you hit Save. In this case, it errored out during the saving process.
Hope this helps! Let me know if you have any questions.
Best regards,
Thao
If you don't have an Amplitude account, you can create an Amplitude Starter account for free and enjoy direct access to the Community via SSO. Create an Amplitude account. You can also create a Guest account below!
If you don't have an Amplitude account, you can create an Amplitude Starter account for free and enjoy direct access to the Community via SSO. Create an Amplitude account. Want to sign up as a guest? Create a Community account.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
