SCM terminates when adding container to a pipeline during startup

SCM terminates when a container in an OPEN state is added to a CLOSED pipeline during SCM startup.
Error:

Cannot add container to pipeline=PipelineID=e7f7dc41-6005-4c8f-8249-f3b021492422 in closed state

Cause:

Container Close happens after the Pipeline Close. The transaction buffer is flushed into SCM DB for every 1000 transactions, the pipeline close comes within the 1000 transaction and it is flushed to the SCM DB but before the Container Close is flushed into the SCM DB the SCM goes.

When the SCM restarts it is in an inconsistent state where some containers are in an OPEN state for a CLOSED pipeline.