This message was deleted.

It can be done by unwrapping the response sequence to stateful behavior, but a more graceful implementation would require an extension that stores the context

I see, thank you very much! Is it possible to filter for a match on a field from a previous request in the scenario? I was able to implement stateful scenarios like the documentation, but no notion of the deviceID is controlled for. If deviceIDs are 000 and 111 Can the state associated with 000 be "Started State 1" while 111's is in "Continue State 2"? Seems like that would then be a non-finite state machine but I may not be thinking creatively enough with matching.