Issue Summary

When a Confluence Cloud page contains many attachment links that point to files attached to other pages , the page may render with the message "We couldn't load the file" on every attachment.

The files themselves are unaffected — opening any of the source pages directly still shows the attachment correctly. The issue only appears when many such cross-page attachment references are rendered together on a single page. A copy of the same page with a smaller subset of the same rows renders correctly, which is the simplest way to confirm that the content itself is valid.

Steps to Reproduce

1. In a Confluence Cloud space, create or migrate a page that contains a large index of attachment links pointing to files attached to many different other pages in the same space 

The relevant tag forms are:

<!-- Inline link to an attachment that lives on another page -->
<ac:link>
  <ri:attachment ri:filename="example-spec.docx">
    <ri:page ri:space-key="EXAMPLE" ri:content-title="Source Page Title"/>
  </ri:attachment>
</ac:link>
 

2. Open the page as a logged-in user with permission to view the source pages.
3. Wait for the page to finish rendering.

Expected Results

All attachment links render normally and can be opened or downloaded as expected, regardless of how many source pages they reference.

Actual Results

Every attachment on the page displays the message "We couldn't load the file". Reloading the page reproduces the same result. The underlying files are intact and remain accessible from their original source pages.

Reducing the number of attachment links on the page (for example, by deleting rows or by splitting the page into smaller child pages) restores correct rendering for the remaining attachments. 

Workaround

Split the affected page into smaller child pages so that no single page references attachments from a very large number of source pages.