This is the same problem you had last month with deploying to dev and Samantha fixed the symlink for you. Scroll up in this channel to Oct 11 for that discussion. For some reason Capistrano isn't updating the symlink to the current deploy properly. Seems to be a recurring problem we need to fix. Create an issue for us to fix later.
For now, you can do what Samantha did and fix the symlink manually. Using sudo, remove the the /srv/apps/curate_uc symlink. Then switch to the scholar user and recreate the symlink pointing to the directory with today's deploy timestamp. Something like
This is the same problem you had last month with deploying to dev and Samantha fixed the symlink for you. Scroll up in this channel to Oct 11 for that discussion. For some reason Capistrano isn't updating the symlink to the current deploy properly. Seems to be a recurring problem we need to fix. Create an issue for us to fix later.
For now, you can do what Samantha did and fix the symlink manually. Using sudo, remove the the /srv/apps/curate_uc symlink. Then switch to the scholar user and recreate the symlink pointing to the directory with today's deploy timestamp. Something like
ln -s /srv/apps/scholar_capistrano/releases/20221103xxxxxx /srv/apps/curate_uc
Replace the xxxxx with the existing directory name from today's deploy. Then restart the app and sidekiq and see if the problem is fixed.