My Job Seems to Be Taking A Really Long Time
The jobs run in the background and for very large jobs, can take many hours or even days to complete. The pre-assembly app should eventually return a status for every job (unless it hangs unexpectedly, in which case you will need to contact the Repository Manager for help). Jobs typically move through the following steps, sometimes very rapidly for smaller jobs:
- Waiting - the job is about to be picked up by a background worker
- Running - the job is currently being worked on (this is the state long running jobs will be in for potentially hours)
- Completed - the job completed successfully with no errors
- Completed (with errors) - the job completed, but one or more objects had an error of some kind. For pre-assembly jobs, this means at least one object failed to accession properly, and you should look carefully at the progress log file. For discovery report jobs, this means one or more objects reported a problem of some kind, and you should look carefully at the discovery report JSON file.
- Failed - the job could not be run at all, possibly due to networking problems or a problem with the manifest or content folder
For any job that fails or completes with errors, the job details page will show the error message:
