You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The CSV Upload tool for Animals, Enclosures and Cohorts is working in development but failing in production with the following error:
Error performing ImportAnimalsJob (Job ID: 123456789) from DelayedJob(default) in 5.79ms: ActiveStorage::FileNotFoundError (ActiveStorage::FileNotFoundError)
We will need to determine what is happening in production to cause this failure and refactor the code to resolve.
This issue is also a good place to discuss the placement of these. Currently they reside on index of each item. This may be confusing from a user experience perspective since we also have the separate Uploads UI. Should these uploads happen through that interface? If a fix for this issue overlaps into a potential refactoring of the UI, we can create additional issues or update this one.
@CraigJZ , I uploaded a few CSV in the staging environment and I dont get an error. However, the status says "Pending". Is there a certain time frame that the status should update? Or does the constant pending status mean something is wrong?
The CSV Upload tool for Animals, Enclosures and Cohorts is working in development but failing in production with the following error:
Error performing ImportAnimalsJob (Job ID: 123456789) from DelayedJob(default) in 5.79ms: ActiveStorage::FileNotFoundError (ActiveStorage::FileNotFoundError)
We will need to determine what is happening in production to cause this failure and refactor the code to resolve.
This issue is also a good place to discuss the placement of these. Currently they reside on index of each item. This may be confusing from a user experience perspective since we also have the separate Uploads UI. Should these uploads happen through that interface? If a fix for this issue overlaps into a potential refactoring of the UI, we can create additional issues or update this one.
#269 also discusses potential import refacting
The text was updated successfully, but these errors were encountered: