How do I define start, end, and reset triggers so operation instances actually collect?

Create an operation definition with start, end, and reset triggers (screen name, AID/action, and field conditions combined with AND), then activate it. Instances appear under Runtime → Operations as traffic matches. Use Retroactive Analysis to backfill historical events without replaying the host. Runtime → Flow needs identified screens and typically 1–10 completed instances; unidentified screens can block Hub creation.