@augustf noticed this one. The issue was narrowed down to the Rails 4.2 migration in core Concerto and appears to be caused by the screen's frontend cache key changing constantly (messages in the console). It might be worth looking into any changes that could have broken the screen's frontend caching method, since the issue no longer occurs when rolling back before the Rails 4.2 branch merge.
@augustf noticed this one. The issue was narrowed down to the Rails 4.2 migration in core Concerto and appears to be caused by the screen's frontend cache key changing constantly (messages in the console). It might be worth looking into any changes that could have broken the screen's frontend caching method, since the issue no longer occurs when rolling back before the Rails 4.2 branch merge.