WildDragonLLC/dragonflight
1
0
Fork 0
Code Issues 32 Pull requests 7 Projects Releases Packages Wiki Activity Actions

fix(worker/thumbnail): mark asset ready even when thumbnail extraction fails

Browse source 
If the thumbnail job throws (network blip, ffmpeg error, short clip), the
asset was left stuck in status='processing' indefinitely. Since the proxy
already exists and the asset is playable, set status='ready' in the catch
block before re-throwing so BullMQ can still record the failure.
This commit is contained in:
Zac Gaetano 2026-05-18 23:51:04 -04:00
parent ff892a1ad5
commit fb3b998cfd
1 changed files with 6 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
services/worker/src/workers/thumbnail.js
View file

@ -64,7 +64,12 @@ export const thumbnailWorker = async (job) => {
return { assetId, outputKey }; return { assetId, outputKey };
} catch (error) { } catch (error) {
console.error(`[thumbnail] Error processing asset ${assetId}:`, error); console.error(`[thumbnail] Error processing asset ${assetId}:`, error);
// Don't set status=error for thumbnail failure — asset is still usable without it // Thumbnail failed but the asset is still usable via proxy — mark it ready
// so it doesn't stay in 'processing' state forever.
await query(
`UPDATE assets SET status = 'ready', updated_at = NOW() WHERE id = $1`,
[assetId]
).catch(e => console.error('[thumbnail] Failed to update asset status:', e));
throw error; throw error;
} finally { } finally {
await Promise.all([ await Promise.all([