I'm encountering a similar problem, but all Expand macros are immediately auto-collapsing. Doesn't matter if I put Expand inside Future, or Future inside Expand.
I made a page that consists only of:

• Future
  • Expand
    • Some plaintext
• Expand
  • Future
    • Some plaintext

And it still exhibits this issue.

Currently on Confluence 7.12.0

EDIT: found a workaround? Setting the Future macro to use manual rendering, and placing Expand inside Future, appears to avoid this issue.

Hi Atlassian,

Can you please expedite this fix? Thank you.

Hello Dear Atlassian!
Would you mind me asking if there are any updates?
We are extremely in need of fixing this bug.

This is there from Confluence 5.3 onwards. I have not checked with version prior to 5.3.

Dear spatro,

Thanks for submitting the ticket
Would you please let me know what affect version of Confluence that you met this issue?

Thanks,
Minh Tran
Confluence BugMaster
Atlassian

Detail analysis for reference

Confluence expand macro binds expand-control elements with "click" and "keyup" events when expand-control found on a page. In case of future macro, since it loads asynchronously, binding occurs multiple times for the expand control which loads first.

Example: There are 2 future embedding expand macros (say future-expand1, future-expand2) on a page.

1. When 1st future loads, there is 1 expand control found on page, that is future-expand1 and it is bound to "click" and "keyup" events.

2. When 2nd future loads, there are 2 expand controls found on page, they are future-expand1 and future-expand2.

• future-expand1 again bound to "click" and "keyup" events.
• future-expand2 bound to "click" and "keyup" events.

3. At the end :

• future-expand1 bound to "click" and "keyup" events TWICE.
• future-expand2 bound to "click" and "keyup" events once.

Since future-expand1 is bound twice with the events, on click or key up, the binding function called twice and every time a binding function called, it toggles the expand/collapse feature of the expand control.

Hence the one that got loaded first expands and collapses instead of just expand or collapse. Where as the last one loaded behaves well (on click either expand or collapse but not both) since its bound to events only once.