Understanding the scfinder log

[dufangqing]

Dear SED-EEW-SeisComP community,

I am writing to seek help to understand some error/warnings in the scfinder log, please see below for a part of my log example:

...
22:22:21 [debug] FinDer epicenter (lat: 44.981995 +- 85.107143 km lon:11.414722 +- 85.140086 km dep: 10.000000) wrapped in origin: Origin/20240305222221.594377.4821
22:22:21 [debug] FinDer magnitude (Mfd: 3.700000, likelihood: 0.693814) wrapped in magnitude Magnitude/20240305222221.594502.4822
22:22:21 [debug] FinDer regression magnitude (Mfdr: 3.700000) wrapped in magnitude Magnitude/20240305222221.594531.4823
22:22:21 [debug] FinDer fault length magnitude (Mfdl: 3.181684) wrapped in magnitude Magnitude/20240305222221.594553.4824
> 22:22:21 [error] Archive version 0.12 too high: StrongOriginDescription skipped
22:22:21 [error] Archive version 0.12 too high: Rupture skipped
22:22:21 [error] Archive version 0.12 too high: Record skipped
22:22:21 [error] Archive version 0.12 too high: PeakMotion skipped
22:22:21 [error] Archive version 0.12 too high: Record skipped
22:22:21 [error] Archive version 0.12 too high: PeakMotion skipped
...
22:22:21 [error] Archive version 0.12 too high: Record skipped
22:22:21 [error] Archive version 0.12 too high: PeakMotion skipped
> 22:22:21 [warning] OX.V109.00.HNE: horizontal gap too high: 60.168004s
22:22:21 [warning] OX.V294.00.HNE: horizontal gap too high: 60.168004s
22:22:21 [warning] OX.V126.00.HNE: horizontal gap too high: 60.168004s
22:22:21 [warning] OX.V009.00.HNE: horizontal gap too high: 60.168004s
22:22:21 [warning] OX.V077.00.HNE: horizontal gap too high: 60.168004s
...

Doubts:

1. for the 'Archive version' too high error, is this related to the strong motion origin and would this error affect the basic origin calculation?
2. for the 'horizontal gap too high' warning, I have already sorted the playback miniseed by endtime, do you have any idea why I would still get this warning and if it would cause the horizontal components to be discarded by scfinder?

Thanks a lot for your time and insights!

Cheers,
Du