In Journey, when a standard task (not a service task) is auto-completed, only the "TaskCompleted" event is generated, not the "TaskStarted" event. This behavior is expected, and the webhook system is working as designed.
Key Details:
Autocompletion Flow: The task begins in the "Preprocessing" state, and when it is auto-completed, it moves directly to the "Done" state.
Event Generation: The system generates a "TaskCompleted" event at the time of autocompletion, but does not generate a "TaskStarted" event, as the task is not explicitly started.
Webhook Behavior: If your webhook is set to trigger on the "TaskCompleted" event, it will fire when the task is auto-completed. However, it will not trigger for a "TaskStarted" event because that event is not generated during autocompletion.
Conclusion:
This is the expected behavior. Since the task does not pass through the "Started" state during autocompletion, only the "TaskCompleted" event is generated, and the webhook for that event will be triggered.