Issue Summary

Partners are experiencing significant delays (up to 70+ minutes) and out-of-order delivery of Confluence events within the Forge platform. This is negatively impacting the usability and data integrity of our app, "Better Content Archiving and Analytics for Confluence."

Steps to Reproduce

1. Perform updates (edits) on various Confluence pages in a customer instance.
2. Compare the eventCreatedDate field in the event payload with the actual time the Forge function is triggered (recorded in Forge logs).
3. Note the consistency of delivery timing and order for multiple rapid updates.

Expected Results

• Events should be delivered with minimal latency (typically < 10 seconds) and processed in a FIFO (First-In, First-Out) manner based on the eventCreatedDate.

Actual Results

Event A:

• • eventCreatedDate: 2025-11-20T14:06:28.579Z
  • Received At: Nov 20, 2025 15:16:11.016
  • Latency: ~70 minutes

Event B:

• • eventCreatedDate: 2025-11-20T14:06:00.975Z (Occurred before Event A)
  • Received At: Nov 20, 2025 15:19:22.212 (Received after Event A)
  • Latency: ~73 minutes

• Events are delayed by over 70 minutes and are not consistently delivered in the order they were created.

Key Observations:

• • Extreme Latency: A delay of over an hour is far beyond the expected near-real-time performance of the Forge event system.
  • *Out-of-Order Delivery: *Event B, which was created ~28 seconds before Event A, was delivered ~3 minutes after Event A.

Workaround

Required, if there is no workaround please state:
Currently there is no known workaround for this behavior. A workaround will be added here when available