Sorry I didn't bet back to this sooner. Not sure what the glitch was, but there's a lot of underlying stuff that LinkedIn and JLinked take care of. If LinkedIn was updating their API's (which happens frequently), there may have been a temporary outage of a specific feature we required during the process.
Glad to hear it's going now. Definitely keep us posted if you see the problem anymore.