DocumentationExperience Cloud KCS

Resolving “Process resource is null” errors in AEM MSM translation workflows

Last update: October 14, 2026

This article explains how to resolve issues where Adobe Experience Manager (AEM) translation projects fail to submit to translation providers due to Process resource is null errors and workflow failures.

Description description

Environment

  • Adobe Experience Manager (AEM), all supported versions
  • Multi-Site Manager (MSM) translation workflows
  • Integration with translation providers such as SDL/Trados

Symptoms

  • Translation projects created in AEM remain in Draft state and don’t proceed to Committed for Translation.

  • Projects aren’t submitted to the external translation provider.

  • The following error appears in AEM logs:

    • com.adobe.granite.workflow.WorkflowException: Process resource is null

  • Additional workflow or crypto exceptions are in the logs.

Cause

A platform-level update or instance restart can result in the runtime copy of the translation workflow model missing its required PROCESS property. This prevents the workflow engine from executing the translation job, resulting in Process resource is null errors and blocking submission to translation providers.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Verify the translation workflow model’s PROCESS property:

    • Access the workflow model editor for your translation workflow (For example: via Tools > Workflow > Models in the AEM Author UI).

    • Locate the translation workflow model used for submitting jobs to your translation provider (commonly named ‘sync_translation_job’ or similar).

    • Identify the Process step responsible for translation submission.

    • Ensure the Process step has the following property set:

    • Name: PROCESS

    • Type: String

    • Value: com.adobe.cq.wcm.translation.impl.process.SyncTranslationProcess

  2. Sync the workflow model to regenerate the runtime copy:

    • In the workflow model editor, make a minor edit (such as updating the description) and save the model.

    • This action forces AEM to regenerate the runtime copy of the workflow model with the correct PROCESS property.

  3. Validate translation job submission:

    • Create a new translation project and attempt to submit it for translation.

    • Confirm that the project proceeds to Committed for Translation and is submitted to your translation provider.

  4. If the Process field appears empty in the workflow model editor:

    • Don’t click Save on the Process step dialog if the dropdown is blank, as this can corrupt the stored value.

    • Simply close the dialog if you observe this behavior.

    • If this issue persists, contact Adobe Support for further investigation.

  5. If you receive a 500 Internal Server Error from the translation provider after the above steps:

    • This indicates an issue on the translation provider’s side. If the error recurs, escalate to your translation provider’s support team.
recommendation-more-help
experience-cloud-kcs-help-kbarticles