Failed redeploys can occur while migrating to Matador

From Manasa:

Based two orders went into error state in post migration step. I think what happened was too many requests were going to the listener too fast and somehow, possibly due to a threading issue the order went into error state. However when I looked at ads logs, both the update requests for both the orders were in success.

Message: Failure detected during campaign deployment 10432c4d 305f 419a b525 2f811777b609. Customer bpID d897e2d2 f8f6 4253 954a 8f950d16b664. Failed advertID list 160.

1259:2014-10-03 03:07:03.304 (3) [pool-3-thread-5]: Finished UPDATE request for campaign d897e2d2-f8f6-4253-954a-8f950d16b664_10612_7963_158_GM: SUCCEEDED
1260:2014-10-03 03:07:03.304 (3) [pool-3-thread-5]: Finished UPDATE request for campaign d897e2d2-f8f6-4253-954a-8f950d16b664_10612_7963_158_GT: SUCCEEDED
1261:2014-10-03 03:07:03.305 (3) [pool-3-thread-5]: Finished UPDATE request for campaign d897e2d2-f8f6-4253-954a-8f950d16b664_10612_7964_159_GM: SUCCEEDED
1262:2014-10-03 03:07:03.305 (3) [pool-3-thread-5]: Finished UPDATE request for campaign d897e2d2-f8f6-4253-954a-8f950d16b664_10612_7964_159_GT: SUCCEEDED
1263:2014-10-03 03:07:03.306 (3) [pool-3-thread-5]: Finished UPDATE request for campaign d897e2d2-f8f6-4253-954a-8f950d16b664_10612_7971_160_GM: SUCCEEDED
1264:2014-10-03 03:07:03.306 (3) [pool-3-thread-5]: Finished UPDATE request for campaign d897e2d2-f8f6-4253-954a-8f950d16b664_10612_7971_160_GT: SUCCEEDED
1265:2014-10-03 03:07:03.307 (3) [pool-3-thread-5]: Finished UPDATE request for campaign d897e2d2-f8f6-4253-954a-8f950d16b664_10612_8114_161_GM: SUCCEEDED
1266:2014-10-03 03:07:03.307 (3) [pool-3-thread-5]: Finished UPDATE request for campaign d897e2d2-f8f6-4253-954a-8f950d16b664_10612_8114_161_GT: SUCCEEDED

Failure detected during campaign deployment 1a8cb794 d4f1 43dc 8af6 a3419f5b9373. Customer bpID 0fd85e9c fd92 44f2 afef ec1802699549. Failed advertID list 108.

1376:2014-10-03 03:07:06.989 (3) [pool-3-thread-5]: Finished UPDATE request for campaign 0fd85e9c-fd92-44f2-afef-ec1802699549_10044_310_107_GM: SUCCEEDED
1377:2014-10-03 03:07:06.990 (3) [pool-3-thread-5]: Finished UPDATE request for campaign 0fd85e9c-fd92-44f2-afef-ec1802699549_10044_310_107_GT: SUCCEEDED
1378:2014-10-03 03:07:06.990 (3) [pool-3-thread-5]: Finished UPDATE request for campaign 0fd85e9c-fd92-44f2-afef-ec1802699549_10044_434_108_GM: SUCCEEDED
1379:2014-10-03 03:07:06.991 (3) [pool-3-thread-5]: Finished UPDATE request for campaign 0fd85e9c-fd92-44f2-afef-ec1802699549_10044_434_108_GT: SUCCEEDED
1380:2014-10-03 03:07:06.992 (3) [pool-3-thread-5]: Finished UPDATE request for campaign 0fd85e9c-fd92-44f2-afef-ec1802699549_10044_675_109_GM: SUCCEEDED
1381:2014-10-03 03:07:06.993 (3) [pool-3-thread-5]: Finished UPDATE request for campaign 0fd85e9c-fd92-44f2-afef-ec1802699549_10044_675_109_GT: SUCCEEDED
1382:2014-10-03 03:07:06.994 (3) [pool-3-thread-5]: Finished UPDATE request for campaign 0fd85e9c-fd92-44f2-afef-ec1802699549_10044_517_153_GM: SUCCEEDED
1383:2014-10-03 03:07:06.994 (3) [pool-3-thread-5]: Finished UPDATE request for campaign 0fd85e9c-fd92-44f2-afef-ec1802699549_10044_517_153_GT: SUCCEEDED

But since the order went into error the post migration script kept going (I am assuming it was polling) and nothing was happening in the backend as the backend (ADS) processed all the requests.

So what I had to do was stop the post migration script (since all the orders except the two were done anyway), go into UI, set the orders to quote and deploy again.
One of these orders were meant to be paused, which could tell, big thanks to Patrick’s tag’s in the comments section.

So after this was done, I confirmed that we had:
10 paused orders
7 deployed (processed orders)
9 orders with location extension (now with feeds)

Before and after migration.