The output at /organiserpanel cuts of at a consistent point (if there have been no changes to the database), depending only on the logged in user. This does not happen locally and we haven't found a way to reproduce it in development environments.