Archive API fails on many archives with "could not resolve reference"

This happens with 1.1 and 1.0. Quite a lot of entries seem effected. See links below.

It looks like an UI error, but its caused by API returning 500 due to exception.

-- Original post The following entry has an unexpected error

entry link

actually this is the case for all the entries that I searched here

Maybe te GUI tests should be much stricter?

Edited Sep 19, 2022 by Markus Scheidgen
Assignee Loading
Time tracking Loading