fix: Backup and restore fixes
All checks were successful
Deploy to Staging / Build Images (push) Successful in 2m20s
Deploy to Staging / Deploy to Staging (push) Successful in 28s
Deploy to Staging / Verify Staging (push) Successful in 6s
Deploy to Staging / Notify Staging Ready (push) Successful in 5s
Deploy to Staging / Notify Staging Failure (push) Has been skipped
All checks were successful
Deploy to Staging / Build Images (push) Successful in 2m20s
Deploy to Staging / Deploy to Staging (push) Successful in 28s
Deploy to Staging / Verify Staging (push) Successful in 6s
Deploy to Staging / Notify Staging Ready (push) Successful in 5s
Deploy to Staging / Notify Staging Failure (push) Has been skipped
This commit is contained in:
@@ -31,10 +31,7 @@ You are a senior software engineer specializsing in NodeJS, Typescript, front en
|
||||
- Research this code base and ask iterative questions to compile a complete plan.
|
||||
- We will pair troubleshoot this. Tell me what logs and things to run and I will
|
||||
- There is a backup system built into the admin settings.
|
||||
- Schedules have been configured but it doesn't appear to be removing old backups
|
||||
- The hourly schedule is set to retain 8 backups but it has over 9 saved.
|
||||
- It is also creating multiple backups per run.
|
||||
|
||||
- Uploading a backup to restore throws a 400 API error.
|
||||
|
||||
|
||||
*** ROLE ***
|
||||
|
||||
Reference in New Issue
Block a user