[SUP-27] FOLIO data export app is failing Created: 10/Dec/20 Updated: 10/Dec/20 Resolved: 10/Dec/20 |
|
| Status: | Closed |
| Project: | Support |
| Components: | Metadata Export |
| Affects versions: | None |
| Fix versions: | 2019 Q4 |
| Type: | Bug | Priority: | TBD |
| Reporter: | Anya | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | |
| Development Team: | None |
| Affected Institution: |
MO State
|
| Description |
|
The short error in the UI is 'ERROR:Cannot read property 'exported' of undefined'. Apparently the failure impacts the back end as well, as I can't run an export using the APIs. CC: Monica Arnold, Brooks Travis, |
| Comments |
| Comment by Anya [ 10/Dec/20 ] |
|
Magda Zacharska- tagging you for awarness. |
| Comment by Anya [ 10/Dec/20 ] |
|
Monica Arnold I have been informed that this is a known issue already fixed in honeysuckle release. That you might be experiencing this issue cause your file is empty. |
| Comment by Monica Arnold [ 10/Dec/20 ] |
|
When I run the process from the command line, it works fine. When I run it from cron, it dies. I'm pretty sure there is a path issued related to the context in which the script runs. I'll try to fix it WITHOUT breaking the system again. Thanks. |
| Comment by Anya [ 10/Dec/20 ] |
|
here is the ticket https://folio-org.atlassian.net/browse/MDEXP-267 |
| Comment by Magda Zacharska [ 10/Dec/20 ] |
|
The observed behavior relates to the fact that the empty file is being sent to trigger the export. This should be handled better by the app and is fixed in the honeysuckle release in scope of
|