Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem: AMClient get_unit_status returns error when unit is in between transfer and ingest #1727

Open
5 tasks
liptakpanna opened this issue Jan 28, 2025 · 0 comments

Comments

@liptakpanna
Copy link

Expected behaviour

Using the AMClient I start a transfer with the create_package method. I get the UUID, and I want to query the status using the get_unit_status to see when it finishes or fails. If the package is still being processed or is waiting in a queue then it should not return an error ideally.

Current behaviour

If the transfer stage finished, but the ingest phase has not been started yet because the workers are too busy then it returns a 400 status code error (Unable to determine the status of the unit ...). But the ingest will start later and the package will be completed, so it is a misleading response.

The problem might be here. If it just returns the ingest status which doesn't exist yet then we lose the valuable information that the transfer was completed without an error and the unit is waiting in a queue.

Steps to reproduce

Send more transfers to an AM instance than it can handle and keep querying every unit UUID quite often to make this error occur.

Your environment (version of Archivematica, operating system, other relevant details)

AM version 1.16, AMClient version 1.2.0


For Artefactual use:

Before you close this issue, you must check off the following:

  • All pull requests related to this issue are properly linked
  • All pull requests related to this issue have been merged
  • A testing plan for this issue has been implemented and passed (testing plan information should be included in the issue body or comments)
  • Documentation regarding this issue has been written and merged (if applicable)
  • Details about this issue have been added to the release notes (if applicable)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant