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.

Sign up for GitHub

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

Jump to bottom

Logs not catching extra instantiation location #912

Open
ekemeyer opened this issue Sep 3, 2024 · 0 comments
Open

Logs not catching extra instantiation location #912

ekemeyer opened this issue Sep 3, 2024 · 0 comments
Labels
Bug softserv propose for softserv

Comments

@ekemeyer
Copy link
Contributor

ekemeyer commented Sep 3, 2024

Describe the bug
When pushing an item from AMS2 with extra instantiation locations to AAPB, it appears to work. There are no indications in AAPB logs that there was an issue, leaving user to believe the push was successful.

To Reproduce
Steps to reproduce the behavior:

  1. Go to record with multiple instantiation locations (see ticket Records/updates don't appear on AAPB when pushed #870 for examples possibly)
  2. Push to AAPB
  3. Review AAPB logs for errors

Additional context
see related ticket #886 where AMS2 is allowing multiple instantiation locations
@ekemeyer ekemeyer added the softserv propose for softserv label Sep 18, 2024
@ekemeyer ekemeyer added the Bug label Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug softserv propose for softserv
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ekemeyer