Cassie, one follow-up, and a question you may be able to answer more easily than I can find out.
The question first. I was told an app partner with a published Marketplace listing has developer support access from the developer account that owns the listing. I tried it today: the Help Center on our developer account offers community and a live chat, the live chat routed me to Sales, and Sales said ticket submission requires a paid account. Is there a support route for an app partner without a paid hub, or is the community the intended channel for API questions? Either answer is fine – I would just like to stop looking.
The follow-up. The property-history ask you offered to pass on has since merged with a second issue, and the pair is a sharper statement than either half. /automation/v4/flows/performance/{flowId} is the only public read of per-flow enrolment volume, and it has no dated successor ahead of the v4 sunset on 30 March 2027 – the 2026-09-beta namespace publishes every sibling path but not that one. Put together with the history finding:
after 30 March 2027 there is no public API surface connecting workflow activity to a workflow at all. Not which workflow wrote a value, and not whether a given workflow runs.
That is a capability the platform has today and would lose, arriving exactly as agent and Breeze actions start running inside workflows. And it has two independent fixes, either of which closes it: a dated flows/performance, or flowId carried alongside sourceId on an AUTOMATION_PLATFORM history entry.
If the version you are passing on is still the history ask alone, this is worth adding – it is the same team’s surface and it makes the case without needing the roadmap answer first. Thread with the detail: /automation/v4/flows/performance has no dated successor ahead of the v4 sunset