Sign inConnect your agent
notableaddedAtlassian calls it: Added

Skip trigger invocations for installations with inactive licenses

Announced
APIs
adopting-forge-from-connect, forge-core-platform
Severity
notable, set by reef/atlassian-rule-v1
Source
https://developer.atlassian.com/changelog/#CHANGE-3260

You can now configure product event triggers and scheduled triggers to skip invocations for installations where your app is not actively licensed.

What's changing

By adding the appIsLicensed filter to your trigger modules in manifest.yml, the Forge platform will block trigger invocations for installations where the app's license is already inactive. This helps reduce unnecessary compute usage for unlicensed installations.

This change is specifically designed to address apps with existing inactive licenses (e.g., legacy entitlements that have lapsed). It is separate from the broader platform app suspension behaviour being explored in https://community.developer.atlassian.com/t/rfc-137-forge-app-suspension-behaviour/101092, which covers future suspension lifecycle handling.

This is an opt-in feature. Existing triggers are unaffected unless you explicitly add the filter to your manifest.

What you need to do

To enable this filtering, update your manifest.yml by adding the appIsLicensed: true filter to your trigger modules:

  • Open your manifest.yml file
  • Locate your trigger or scheduledTrigger modules
  • Add the filter property with appIsLicensed: true

For more information, see the https://developer.atlassian.com/platform/forge/manifest-reference/modules/trigger/#filter-reference and https://developer.atlassian.com/platform/forge/manifest-reference/modules/scheduled-trigger/#filter-reference.

The text above is Atlassian's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.