Overview

The Herzum Approval App for Cloud operates within the limits imposed by Atlassian Forge, which enforces specific quotas and restrictions to ensure optimal performance and stability. These limits are not set by the Herzum Approval App but by Atlassian and apply to all Forge apps.

For more details, visit the official Atlassian site Platform quotas and limits​

Atlassian Forge Limits

1. Invocation Rate Limit

   • Maximum: 500 invocations per 25-second sliding window.

   • Explanation: The app can handle up to 500 actions or requests within any 25-second period. Surpassing this limit may temporarily block app functionality until the window resets.

2. Runtime Seconds

   • Maximum: 25 seconds of runtime per operation, including UI modules invoked by Forge remote.

   • Explanation: The app must complete any single operation within 25 seconds, after which it will be stopped by Forge.

3. Read Operations

   • Maximum: 1000 read operations every 20 seconds.

   • Explanation: Data retrieval operations, such as fetching issue details or user information, are limited to 1000 within a 20-second window.

4. Events Per Minute

   • Maximum: 500 events pushed per minute.

   • Explanation: This limit governs the number of event notifications the app can send or process within a minute.

Herzum-Specific Control on Limits

To ensure smooth operation and compliance with these quotas, the Herzum Approval App restricts the number of simultaneous approval flows to 30. This limit helps prevent overloading the app and ensures users avoid hitting Atlassian-imposed thresholds.

Example Scenario

A basic approval flow in the Herzum Approval App requires approximately 60 requests on average. Here's how this usage interacts with Atlassian Forge limits:

• Invocation Rate Limit: If 10 users initiate approval flows simultaneously, it would generate approximately 600 requests (10 flows x 60 requests). This exceeds the 500-invocation limit for a 25-second window. Consequently, app performance could be affected until the window resets.

• Read Operations: Assuming each flow involves 30 read operations, 30 simultaneous approval flows would use 900 read operations, approaching the 1000 read operation limit within 20 seconds.

• Event Notifications: 30 flows would generate approximately 180 events (30 flows x 6 events), which stays well within the 500-event limit per minute.

Important Notes

1. Atlassian Enforced Limits
   These limits are imposed by Atlassian Forge and are beyond the control of Herzum Approval App. Any disruption caused by exceeding these thresholds is a result of Atlassian's platform rules.

2. Best Practices

   • Limit simultaneous approval flows to ensure requests remain within Atlassian-imposed limits.

   • Spread out high-volume operations over time to reduce the risk of hitting rate limits.

By adhering to these recommendations, you can ensure smooth usage of the Herzum Approval App while staying compliant with Atlassian Forge quotas.