Thank you for the explanation @yanjingzhu … I am completely confused, however.
I am not implicitly defining any types, but rather I am explicitly defining no types.
If I implicitly do not define any types, I would expect all types to be enlisted. However, if I explicitly define types – even and especially when there are none – I would expect the types that I have taken the time to explicitly define to be the only events that I want to enlist to trigger the workflow.
How does explicitly defining no types default to all types? This seems backward and broken.
> You can limit your workflow runs to specific activity types using the types keyword.
That is exactly what I am trying to do, by explicitly defining no types, not all of them.
This seems and feels like a bug, but perhaps I am misunderstanding something.