Skip to content

Conversation

@zackpollard
Copy link
Member

@zackpollard zackpollard commented Mar 5, 2025

When files had failed to move previously, and were then re-uploaded (or two files had the same path) the storage template system would get itself into a situation where the file could never be moved. This resolves that by cleaning up the move history table when an asset is deleted, and also does a bulk cleanup when the job is run manually.

Fixes #16354

@zackpollard zackpollard force-pushed the fix/storage-template-conflicts branch from db9a679 to 58589bd Compare March 5, 2025 14:01
@zackpollard zackpollard force-pushed the fix/storage-template-conflicts branch from 58589bd to c18b445 Compare March 5, 2025 14:04
@zackpollard zackpollard force-pushed the fix/storage-template-conflicts branch from c18b445 to d97aa82 Compare March 5, 2025 14:16
@zackpollard zackpollard merged commit 9922c8d into main Mar 5, 2025
42 checks passed
@zackpollard zackpollard deleted the fix/storage-template-conflicts branch March 5, 2025 15:00
zackpollard added a commit that referenced this pull request Mar 5, 2025
fix: storage template breaks when files are re-uploaded after a move failure
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

duplicate key value violates unique constraint "UQ_newPath"

3 participants