SIPActions.create_package fails when last_started and next_queued have different pipelines
Closed this issue · 0 comments
bonniegee commented
Describe the bug
SIPActions.create_package instantiates the Archivematica client from the next_queued SIP, and then checks to see if the last_started SIP has finished processing. If the next_queued SIP is in a different AM pipeline than the last_started SIP, AM cannot find the transfer (because it's in a different pipeline) and the routine fails.
To reproduce
Create a SIP that has a different pipeline than the previously started SIP.
Expected behavior
The last_started check should be filtered to SIPs that have the same origin as the next_queued SIP.