-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Medium
-
Component/s: Page - Attachments (Image, Video, etc.)
-
None
-
2
-
Severity 3 - Minor
-
1
Issue Summary
When a page's images have a Media metadata response that omits the original
rendition node, Confluence treats the resulting parse failure as a temporary
transport error. It retries each failed lookup 3 times and caches nothing, so the
lookup repeats on every render pass - roughly 54 Media calls for a page with 5 such
images.
That exceeds Confluence's 10 second body-render limit, so the body render is
abandoned and the request fails with a 504. The user sees a blank page.
The metadata is only an optional layout hint, and Confluence already degrades
gracefully when it is missing. The bug is the ~25 seconds spent before reaching that
fallback.
Steps to Reproduce
- Open a page with multiple images whose Media metadata response is missing the
original rendition (commonly seen on DC to Cloud migrated attachments). - Wait for the page to load.
Expected Results
The page body renders. Images with no usable metadata render without intrinsic-size
hints (minor layout shift, larger download); the rest of the page is unaffected.
Actual Results
The page body does not render at all. The request takes ~25-28 seconds and fails:
The underlying service call timed out (504)
Workaround
None