What causes "Can't handle RequestMessage(...) after being flush" ?

`
13:05:56.821 [DEBUG] i.g.c.c.Controller - Ignore message UserMessage(Individuals (individual),1441544411922383498-4470,End,1422295312980,1422295443661) while waiting for DataWriter to terminate

13:05:56.874 [DEBUG] c.n.h.c.p.n.h.Processor - Channel Closed: [id: 0x8374d4f0, /10.25.150.57:54371 :> pvs-api.cigna.com/170.48.27.70:443] with attribute INSTANCE

13:05:56.890 [DEBUG] c.n.h.c.p.n.h.Processor - Channel Closed: [id: 0x66837e83, /10.25.150.57:54276 :> pvs-api.cigna.com/170.48.27.70:443] with attribute INSTANCE

13:05:56.945 [DEBUG] i.g.h.a.HttpRequestAction - No attribute named ‘SURVEY_RESPONSE_ID’ is defined

13:05:56.945 [INFO ] i.g.c.r.w.FileDataWriter - Can’t handle RequestMessage(Survey Submission (individual),1441544411922383498-7265,List(),SurveyResponses.PUT,1422295556945,1422295556945,1422295556945,1422295556945,KO,Some(No attribute named ‘SURVEY_RESPONSE_ID’ is defined),List()) after being flush

13:05:56.945 [INFO ] i.g.c.r.w.ConsoleDataWriter - Can’t handle RequestMessage(Survey Submission (individual),1441544411922383498-7265,List(),SurveyResponses.PUT,1422295556945,1422295556945,1422295556945,1422295556945,KO,Some(No attribute named ‘SURVEY_RESPONSE_ID’ is defined),List()) after being flush

13:05:57.064 [INFO ] i.g.h.a.HttpRequestAction$ - Sending request=SurveyResponses.PUT uri=https://pvs-api.cigna.com:443/services/v1/surveyresponses/767bf1d2-1203-4aa2-97e9-5c5333ac2abe?access_token=ea46252e-5746-4635-abd0-413fa8fd688c: scenario=Survey Submission (individual), userId=1441544411922383498-7006

13:05:57.074 [INFO ] i.g.h.a.HttpRequestAction$ - Sending request=SurveyResponses.PUT uri=https://pvs-api.cigna.com:443/services/v1/surveyresponses/6008ad04-33f0-4c78-91ee-6473177025f9?access_token=86efb412-246f-4c0e-b12e-70b5656c9d4d: scenario=Survey Submission (individual), userId=1441544411922383498-7357

13:05:57.135 [INFO ] i.g.h.a.HttpRequestAction$ - Sending request=SurveyResponses.PUT uri=https://pvs-api.cigna.com:443/services/v1/surveyresponses/a45f9e18-7a32-43bd-a49c-35e0c6d8460b?access_token=14614a1c-42ce-4623-93dc-f2b83c27799a: scenario=Survey Submission (individual), userId=1441544411922383498-7337

13:05:57.172 [DEBUG] i.g.c.c.Controller - Ignore message UserMessage(Incentives (individual),1441544411922383498-3645,End,1422295210624,1422295443662) while waiting for DataWriter to terminate

13:05:57.172 [DEBUG] c.n.h.c.p.n.h.HttpProtocol -
`

This happened after what I assume is maxDuration trying to terminate the running scenario(s).

Some request info arriving during/ after shutdown. Cope with it.

I thought it was something like that.

I’m trying to figure out why a 15 minute run, started on Friday, was still running this morning… If I find something actionable, I’ll let you know.