Users who get shown a movie in the 'Training' (or other similar voting intents) and locks their phone for several mins (say they jump on the underground with no internet for 15mins) the contexts die & the user experiences a 'no contexts exist' situation when they click on the 👍 or 👎 suggestion chips.
Perhaps the problem is that because contexts die after x time, we cannot rely on them during conversations, where the user has been offline for a sustained period of time.
TODO: Check the last Conversation ID (stored in user|conv storage) when relying on existence of contexts, if the conversation ID has changed then we could say "Things changed, let's start fresh!" instead of pushing a hard error to the user.
Users who get shown a movie in the 'Training' (or other similar voting intents) and locks their phone for several mins (say they jump on the underground with no internet for 15mins) the contexts die & the user experiences a 'no contexts exist' situation when they click on the 👍 or 👎 suggestion chips.
Perhaps the problem is that because contexts die after x time, we cannot rely on them during conversations, where the user has been offline for a sustained period of time.
TODO: Check the last Conversation ID (stored in user|conv storage) when relying on existence of contexts, if the conversation ID has changed then we could say "Things changed, let's start fresh!" instead of pushing a hard error to the user.