Adding unknown revision or manifest ids breaks timeline
|Reported by:||Owned by:||Thomas Moschny|
If, in a ticket, you include a revision id or manifest id that is not in the mtn database then the timeline then breaks. Further, it does not recover when the id does appear in the mtn database (e.g. as the result of a sync). The current work-around is to clear out the cache.