The sales process expects an awareness call and then a discovery call. On a smaller account both can happen in a single sitting, and the process had no way to record that. The lead stopped at a step the work had already satisfied.
- The satisfying logic already existed and nothing about the process changed. An appointment marked as the discovery booking ticks the booking step when it is created and the call step when it is closed, so one appointment covers both. The booking gate is never skipped. It is satisfied by a record standing for a meeting that genuinely happened.
- A decline type was added to the task. Declining a step already means the work did not happen, and compression makes the same keystrokes also mean it happened elsewhere. Without a field to tell those apart, an automation reading the free text reason would create a record of a meeting that never took place.
- The new automation writes no attendee of any kind, and refuses to act when there is no source meeting to compress into. It can record a real meeting and cannot invent one. That was verified on a record the automation itself created, not only on its design.
- It deployed clean, switched on clean, and did nothing. A run whose condition is false still reports success, and a second fault killed every later run with a message that named no step. Both were found by reading the records rather than the run status.