If this is a Railway volume backup, the restore flow has one easy-to-miss step: restoring the backup stages a project change, but it does not finish until you open the staged changes/details panel and click Deploy.

I would check this sequence:

1. Go to the service that owns the volume/backup, not the consuming app by name. In this case check whether the backup ID 0087c9ff-527c-416a-b537-53371545b8ed belongs to the volume attached to gym-api in the same project + environment.
2. 2. In that service's Backups tab, click Restore on the backup. Wait for the staged change to appear.
3. 3. Open the Details/staged changes panel on the project canvas. You should see Railway adding a new volume mounted at the same path and unmounting the previous volume.
4. 4. Click Deploy to apply the restore. Until that deploy happens, it can look like the backup is "not deploying" because the restore is only staged.

Two caveats from the docs that may explain this if the button/action is missing: backups can only be restored into the same project + environment, and wiping a volume deletes its backups. If the backup came from another environment or the original volume was wiped/recreated, staff may need to inspect that backup ID directly.