jormungandr: Block created but not accepted by the network without any information as to why

Describe the bug I was scheduled for a block at

- created_at_time: "2019-12-30T12:29:37.841257060+00:00"
enclave_leader_id: 1
finished_at_time: "2019-12-30T12:36:17.006271651+00:00"
scheduled_at_date: "16.31280"
scheduled_at_time: "2019-12-30T12:36:17+00:00"
status: 
  Block:
    block: 2a4e3cfcf0e542ef3961b189562d21d1f74305d65f050a67914f044c7442d97a
chain_length: 55079
wake_at_time: "2019-12-30T12:36:17.003739280+00:00"

Block was produced as per log entries below; however is not included in the chain according to shelley eplorer; the parent block is.

[mark_stopka@nlgc-bltn-docker-host-01 ~]$ docker logs db4075d86859 2>&1 | grep 2a4e3cfcf0e542ef3961b189562d21d1f74305d65f050a67914f044c7442d97a
Dec 30 13:36:17.071 INFO receiving block from leadership service, date: 16.31280, parent: 915dd3b85c5a31406bbdaa65889827c90a5ede05b5d6c648e4bb5ae30c7464d9, hash: 2a4e3cfcf0e542ef3961b189562d21d1f74305d65f050a67914f044c7442d97a, task: block
Dec 30 13:36:17.128 INFO block from leader event successfully stored, date: 16.31280, parent: 915dd3b85c5a31406bbdaa65889827c90a5ede05b5d6c648e4bb5ae30c7464d9, hash: 2a4e3cfcf0e542ef3961b189562d21d1f74305d65f050a67914f044c7442d97a, task: block
Dec 30 13:36:17.128 INFO update current branch tip, date: 16.31280, parent: 915dd3b85c5a31406bbdaa65889827c90a5ede05b5d6c648e4bb5ae30c7464d9, hash: 2a4e3cfcf0e542ef3961b189562d21d1f74305d65f050a67914f044c7442d97a, task: block

Mandatory Information

1. jcli --full-version output;

[mark_stopka@nlgc-bltn-docker-host-01 ~]$ docker exec -ti db4075d86859 jcli --full-version
jcli 0.8.5 (HEAD-3db06807, release, linux [x86_64]) - [rustc 1.40.0 (73528e339 2019-12-16)]

1. jormungandr --full-version output;

[mark_stopka@nlgc-bltn-docker-host-01 ~]$ docker exec -ti db4075d86859 jormungandr --full-version
jormungandr 0.8.5 (HEAD-3db06807, release, linux [x86_64]) - [rustc 1.40.0 (73528e339 2019-12-16)]

Expected behavior Block will either be included in the blockchain or an information referencing the same block hash will be provided as to why the block was not accepted by the network.

Additional context Slot 16.31280 was no filled by any other blocks. It seems the parent block should’ve been different with block from slot 16.31267, however once Jormungandr realizes this situation an information with a logging level WARN or higher should have been issued. Part of that information should also be the hash of the rejected block for easy event correlation.