Pixel stays on after schedule ends

My first year with pixels and going well except one small thing... most nights one pixel stays on after the end of the schedule time, like it freezes. Usually the last pixel in the chain (a floodlight) but not always. Fixed by disconnecting and reconnecting power. I have a Rasp Pi running FPP with Hanson rPi-28D cape with the two WS281X ports used, around 300 pixels in total. Schedule by Xlights.

I think that there's a "turn off at end" setting somewhere in Falcon Player.
Another cause can be if you don't have the right number of pixels assigned and that last pixel is actually just getting some spurious data. Turn what you believe is the last pixel on with xlights and/or FPP and confirm that it is the pixel you think it is.
Pixels will actually stay with the last data that they get forever or until the power is cycled. That's why you need to confirm that it's actually getting it's right data and that it is told to turn off at the end of the show.

Thanks Alan. The pixel count in the FPP was one too high (from when I removed a faulty pixel). The sequence has just turned off and all pixels are now off. Hopefully has fixed the problem for good.

Even after all the careful planning, I still managed to stuff up the pixel counts on a few occasions.
Turning on each element / model by itself is a great way to check.

Glad it was such a simple fix for what seemed like a weird issue.