Lighthouse service sometimes fails to update

I use the service broker to integrate Bitbucket with Lighthouse, and it is usually wonderful…except sometimes when the occasional changeset fails to show up in Lighthouse. This can be problematic when one uses commit message keywords to track ticket states.

Of course, since I can’t monitor the traffic between the services, I have no idea where the problem lies (with you, or with them), and since it is an occasional issue it is not easy to reproduce.

In case it helps, an example of a changeset that failed to show up in Lighthouse was https://bitbucket.org/erezlife/erezlife/changeset/850971b64d20 (n.b. private repo). With luck you have logs to track this; if not, well, I would very much like to provide more helpful info but I don’t know how to reproduce it!

Another example: http://bitbucket.org/erezlife/erezlife/changeset/774c2d328a4b