What is the challenge? |
At times, events captured by the webhook can take up to an hour to be received. This delay is inconsistent - sometimes responses are near real-time, other times significantly slower. |
|---|---|
What is the impact? |
Delays in receiving webhook events impacts downstream automations and data synchronization. We utilize custom automations that the native automation tool cannot support. For example, we have two portals linked to two separate workspaces. While ideas from both portals can be linked to the same features, the required status synchronization depends on which workspace the idea belongs to. We handle this unique case entirely through webhook events. If there’s a delay in receiving a feature status change event, the corresponding idea status update is also delayed. |
Describe your idea |
Improve the webhook processing engine to ensure consistent, low-latency delivery of events, similar to that of the Jira webhook which is consistently fast. The goal is to deliver webhook events in near real-time regardless of system load. |
Thanks for sharing this detailed feedback. We recently improved our activity webhook queuing to reduce delivery delays and provide more consistent processing. Please let us know if you continue to see slow or inconsistent behavior.
We’re also experiencing similar issues, having developed a bespoke integration between Aha! and Agility (by Digital.ai).
Even with “Reduce webhook delay” enabled, webhook delivery is highly inconsistent — ranging from near real-time to delays of up to ~45 minutes.
This makes it extremely difficult to build reliable downstream automations and integrations, particularly for time-sensitive actions like creating corresponding records in the target system.
More predictable, low-latency webhook delivery would significantly improve operational reliability and strengthen end-user confidence.