Discussions

Our app uses the LiveAvatar API to create and delete contexts. When a session ends, we call stopSession and then deleteContext(dynamicContextId) in that order. Despite this, our LiveAvatar dashboard shows many contexts (175+), and the count keeps growing.
What might cause deleteContext not to remove contexts in practice? For example, could the delete fail because it runs too soon after stopSession, or are there other requirements (auth, timing, rate limits, etc.) that we might be missing? We want to ensure contexts are cleaned up when sessions end.