I know this has occurred occasionally in the past, but did you folks notice it happening more often with the new build 101?
Regardless, I'd recommend assigning the FFB Reset button as privatebrian says, in case it happens again. I've actually been able to reproduce this bug in the debugger, and we don't seem to be getting any error codes back so it looks like everything is working fine from our point-of-view. In other words, there's no way for us to detect that your FFB isn't currently working!
I know this has occurred occasionally in the past, but did you folks notice it happening more often with the new build 101?