Something odd started happening last night.  Whenever any of my players would make a roll in D&D Beyond:

• For the person making the roll, everything would behave normally (die would roll on their screen, Gamelog would show them the result)
• For everyone else, we could see that a roll was being made, why type of skill and die was being used, but it would stay in a "pending" state.
  • If we refreshed our browser, we'd see the result of all the "stuck" rolls.
• The behavior was consistent for all 5 of my players and myself.
• We're playing remotely (all of us at different locations/internet connections)
• Behavior occurred regardless of how the roll was generated (Desktop Web or Mobile App) 

What's strange is that it seemed to be related to our Campaign.  I have a test/dummy campaign, and the game log functions fine for that one.

Help?

Unfortunately I have no solution but our campaign is experiencing the same issue (and it seems to be breaking some Avrae integration). Very similar circumstances.

It does seem to be campaign specific.  This campaign has the issue, but this campaign does not.

All players are remote for both, though two of the players for the second campaign are on the same connection.  I saw the same issue as you, our rolls would show on our own sheets and populate there but the log would only show "..." until reloading the page.  Waiting for reasonable amounts of time did not make it populate, only refreshing the page.

Quote from dertechie >>

Unfortunately I have no solution but our campaign is experiencing the same issue (and it seems to be breaking some Avrae integration). Very similar circumstances.

It does seem to be campaign specific.  This campaign has the issue, but this campaign does not.

All players are remote for both, though two of the players for the second campaign are on the same connection.  I saw the same issue as you, our rolls would show on our own sheets and populate there but the log would only show "..." until reloading the page.  Waiting for reasonable amounts of time did not make it populate, only refreshing the page.

 
Well, not sure what if anything was done... but the issue appears to have resolved itself for my campaign.