throttle limits are being utilized across different journeys

[Praveenku32]

Hi Team,

We are currently trying to understand how the throttle limits are being utilized across different journeys.

For example:

Let’s say we have defined a throttling rule of 200 calls per second. Our system is triggered by a custom action across 10 different journeys. If one journey receives 300 calls per second, it will consume all 200 available slots, and the remaining 100 calls will either be discarded or queued. As a result, the other 9 journeys will not have any slots left due to the exceeded limit.

We would like to identify:

• Which journey received the 300 calls per second?
• Which journeys were impacted and did not receive any slots?

Do you know of any method or API that can help us pull these logs or provide visibility into this usage?

Thanks in advance for your help!

[SatheeskannaK · Accepted solution]

@Praveenku32 I believe some of these calls get recorded as insights in the developer console.

https://developer.adobe.com/developer-console/docs/guides/insights