AMS2 runs digital instantiation ingests twice if they're bigger than it likes

[ekemeyer]

Details

Hi, as the title suggests, AMS2 does a weird thing where if I run a digital instantiation ingest that's bigger than it likes (it seems to cap out at about 1500), it will stop the AMS2 and then run the ingest twice (see batches 3434 and 3435). It then runs through fine, but doubly. I've so far only noticed it on digital instantiation ingests (asset-level ingests don't seem to be affected). IDK if this is a bug or what, but just letting you know that it does this!

Submitted by: Miranda Villesvik
CC in communications:
Priority: Low (whenever)
URL:
Slack message thread: