That error typically means that the job scheduler needs to be restarted. See:
Note that in 2.5, the job scheduler also has a restart limit (of 3 restarts within 24 hours), to prevent it from getting caught in a loop and trying to restart itself endlessly. You can reset this count with:
- sudo systemctl reset-failed atom-worker
You can also check the status of the atom-worker to make sure it restarted properly with:
- sudo systemctl status atom-worker
See the commands at the bottom of this section:
If you know the date range you want to update the parent description with, you can always do this manually, simply by entering edit mode on your archival description, navigating to the Dates of creation area, making the changes to the current date range, and then saving your description. You may still get a 500 error if you don't first restart the job scheduler however, because a background job is typically triggered on an archival description update to asynchronously update any affected linked records (such as authority records, etc).
Let us know how it goes!