I am only getting started, but as I work through the API and logistics for my use-case, I came across this post. It feels kinda silly that we can’t make a call to the API and query our active conversations.
Yes, this is potential scope creep on this chain, but setting a timeout for a conversation, and then being able to lookup active conversations via the API would make things a heck of a lot easier IMHO. Current state is two sets of code versus business logic built right into the domain or another config file.
Just my ten cents, and the only reason I can add to this question is because I am really jamming along now with the 1.0 + workflow that you enabled.