Degraded Extraction Service Following v1.70.1.0 Release

The issue has been resolved with a patch to the workflow logic. Additional logging and failsafe measures have been added to prevent recurrence. The Extraction pipeline is now fully operational.

We’ve been monitoring behavior across our lower environments to ensure the fix addresses the identified issue effectively.

The root cause has been confirmed as a workflow misconfiguration that routed unsupported files to the extraction stage. This caused avoidable failures during processing. The Extractor component was behaving as expected under the circumstances.

After recreating several failed scenarios and analyzing their processing trail, our team identified that the issue was not rooted in the Extractor module itself, as initially suspected. Instead, we discovered that some non-extractable files were inadvertently entering the extraction workflow due to a misconfiguration.

We are investigating an issue that is leaving some files processed in failed states.