Field deployment fails with 'No async deployment job ID found.'

A user reported this to me and it was quite simple to reproduce. This seems to be regression in the CLI as it's simple to reproduce from the command-line as well, and it has been reported in the CLI GitHub issue tracker:

https://github.com/forcedotcom/cli/issues/639

If you're encountering this issue, I encourage you to weigh in on the linked issue above to show the impact of this issue.

Note that as a workaround until it's fixed, you can deploy the entire parent object.

Comments (2)