Handling errors in document processing workflows

Use structured error handling to keep document workflows predictable. Validate inputs before processing, catch SDK exceptions, and return clear messages when operations fail.

Download sample

How Nutrient supports this workflow

Nutrient Python SDK uses Python’s exception model and raises NutrientException when an operation fails.

You don’t need to manage:

  • Low-level error code interpretation
  • Partial failure state handling
  • Resource cleanup logic after failures

Use standard Python try/except patterns to control error flow in your application.

Complete implementation

This example shows one way to validate input, run conversion, and handle failures.

Import the required SDK classes and pathlib for file validation:

from pathlib import Path
from nutrient_sdk import Document
from nutrient_sdk import NutrientException

Create a dedicated function for conversion so main can handle errors at the call site:

def convert_document(input_file, output_file):
    with Document.open(input_file) as document:
        print("Document opened successfully.")
        print("Converting to PDF...")
        document.export_as_pdf(output_file)

In main, validate the input path, call convert_document, and catch NutrientException to report actionable output:

def main():
    input_file = "input.pdf"
    output_file = "output.pdf"


    if not Path(input_file).is_file():
        print(f"Error: Input file '{input_file}' not found.")
        raise SystemExit(1)


    print(f"Opening document: {input_file}")


    try:
        convert_document(input_file, output_file)
    except NutrientException as e:
        print(f"Nutrient SDK Error: {e}")
        raise SystemExit(1)




if __name__ == "__main__":
    main()

Summary

The error handling flow has three steps:

  1. Validate that the input file exists.
  2. Open the document and run conversion.
  3. Catch NutrientException and return meaningful feedback.

Nutrient raises NutrientException for SDK failures, so you don’t need to implement custom low-level error parsing.

You can download this sample package to run the example locally.