Due to unreliable network environment,
we'd randomly experience packet lost in network traffic.

Hence,
when an Upstream Jenkins job triggered a Downstream Jenkins job in Post-Build action,
sometimes we found from Upstream Console Log that Upstream did trigger the job,

Triggering a new build of $Downstream

but Downstream job didn't start at all.

We suspect it's that trigger package is lost on a way to Jenkins master.
But I'd like the plugin to be able to handle this case,
and mark the Upstream job as unstable or failure depends on the config
instead of silently finished the job as successful.