1
00:00:00,720 --> 00:00:05,390
There is one other small change we're going to make to our expiration complete listener right now.

2
00:00:05,400 --> 00:00:09,820
Whenever we receive a message we're going to find a corresponding order no matter what.

3
00:00:09,930 --> 00:00:12,770
And always mark the order has been cancelled.

4
00:00:12,900 --> 00:00:16,150
As you can imagine there might be a kind of big downside to this.

5
00:00:16,200 --> 00:00:21,720
What would happen if we received a cancellation event around an order that has already been paid for.

6
00:00:21,720 --> 00:00:26,250
Well chances are we would take this order that has already been paid for already marked as complete

7
00:00:26,520 --> 00:00:31,290
and cancel it anyways so we do have to add in a little check here and just make sure that we do not

8
00:00:31,290 --> 00:00:35,910
try to cancel an order that has been paid for right after our little check to make sure that we have

9
00:00:35,910 --> 00:00:37,150
an order.

10
00:00:37,260 --> 00:00:42,420
We're gonna take a look at the order status property and we're going to say that if this is equal to

11
00:00:42,750 --> 00:00:49,950
order status not complete then let's just return early act the message because we do not want to do

12
00:00:49,950 --> 00:00:51,850
anything with this cancellation event.

13
00:00:52,260 --> 00:00:59,750
So I'm going to return early and call message dot back like so ok good little fix because right here

14
00:00:59,780 --> 00:01:01,160
and continue in just a minute.