An IDE-managed application server finished compiling and preparing its artifact, but the server never reached deployment. The decisive message was not a compiler error. It was a debugger listener failure: the configured address could not be bound because it was already in use.

The usual explanation …

A minimal audio smoke test produced a WAV file that played normally, yet FFmpeg printed two alarming messages near the end of the file:

Packet corrupt
corrupt input packet in stream 0

Treating any occurrence of corrupt as a failed generation would have discarded usable audio. Ignoring the warning …

A newly created outbound order could be found by its exact order number, but it did not appear when the default order-status dashboard opened. The API returned no authorization or warehouse-scope error, so the behavior initially looked like a missing SQL condition or stale cache.

Comparing the two …