Hi all,
I’m running into some unexpected behavior while implementing a Forge install event handler (avi:forge:installed:app). In practice we see a context field embedded directly in the install event payload that contains things like the site’s ARI or cloudId.
This works and our other apps rely on it, but the official lifecycle events documentation only lists a small set of top-level properties (id, installerAccountId, app, environment) and doesn’t show or describe this context property at all. That makes it feel pretty brittle to rely on in production — especially when we’re depending on it as a tenant identifier.
There’s a great thread already about this here:
https://community.developer.atlassian.com/t/forge-site-id-documentation/97338 — but the last update just mentions that documentation might be added soon.
So my question is:
Is the presence of the context/siteId/cloudId fields inside the install event payload considered a supported and stable part of the Forge API contract?
Thanks for any updates or guidance!