# Migration from 2.3.1 to 3.0.2: await

**URL:** <https://community.gatling.io/t/migration-from-2-3-1-to-3-0-2-await/4726>\
**Category:** Gatling (Open-Source)\
**Created:** [December 24, 2018, 4:44pm UTC](https://community.gatling.io/t/migration-from-2-3-1-to-3-0-2-await/4726 "2018-12-24T16:44:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Katerina\_Stepanova](https://avatars.discourse-cdn.com/v4/letter/k/54ee81/32.png) [@Katerina\_Stepanova](https://community.gatling.io/u/Katerina_Stepanova)\
**Post date:** [December 24, 2018, 4:44pm UTC](https://community.gatling.io/t/migration-from-2-3-1-to-3-0-2-await/4726/1 "2018-12-24T16:44:01Z")

</div>

Hi!  
I’m trying to migrate my load tests project to Gatling 3.0.2.  
And I cannot think of a way to wait for responses on websocket in my specific case.

Here’s what I’ve got:  
I’m sending some request, and as a result I receive several messages:

1. Several messages indicating progress - number of these messages is not fixed and cannot be predicted in any way (as is depends among other things on current load on server etc.)
2. A resulting message that I actually need.

So i thought I need to set a check which would match message #2 and have some reasonable timeout (like in 2.3.1).  
But it always fails when the 1st of messages #1 is received.  
Also there are other messages coming from time to time from the server not related at all to any requests i send, that could also come in between my request and response.

I could not think of any way to circumvent this limitation.

Or maybe I’m doing it wrong?