Issue: Error running sweep for be1a1c41-0207-4d0f-b02c-b8b222bbf00495 java.lang.NullPointerException: Workflow definition is null

[pankajthamkeappdirect]

Hi Team,
We are facing the below issue in conductor version 3.3.5. We are using conductor with mysql database. I tried disabling the WorkflowRepairService using property conductor.workflow-repair-service.enabled=false but it did not work. Could you please let us know what is causing this issue ?
Error running sweep for be1a1c41-0207-4d0f-b02c-b8b222bbf00495java.lang.NullPointerException: Workflow definition is null

logs:
33886 [sweeper-thread-0] ERROR com.netflix.conductor.core.reconciliation.WorkflowSweeper [] - Error running sweep for 68b6fa03-43b3-40eb-9523-a5d2886cf151 java.lang.NullPointerException: Workflow definition is null at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:897) ~[guava-30.0-jre.jar!/:?] at com.netflix.conductor.common.run.Workflow.getWorkflowName(Workflow.java:385) ~[conductor-common-3.4.0-SNAPSHOT.jar!/:3.4.0-SNAPSHOT] at com.netflix.conductor.core.metadata.MetadataMapperService.lambda$populateWorkflowWithDefinitions$1(MetadataMapperService.java:89) ~[conductor-core-3.4.0-SNAPSHOT.jar!/:3.4.0-SNAPSHOT] at java.util.Optional.orElseGet(Optional.java:369) ~[?:?] at com.netflix.conductor.core.metadata.MetadataMapperService.populateWorkflowWithDefinitions(MetadataMapperService.java:88) ~[conductor-core-3.4.0-SNAPSHOT.jar!/:3.4.0-SNAPSHOT] at com.netflix.conductor.core.execution.WorkflowExecutor.decide(WorkflowExecutor.java:1118) ~[conductor-core-3.4.0-SNAPSHOT.jar!/:3.4.0-SNAPSHOT] at com.netflix.conductor.core.reconciliation.WorkflowSweeper.sweep(WorkflowSweeper.java:72) ~[conductor-core-3.4.0-SNAPSHOT.jar!/:3.4.0-SNAPSHOT] at com.netflix.conductor.core.reconciliation.WorkflowSweeper.sweepAsync(WorkflowSweeper.java:57) ~[conductor-core-3.4.0-SNAPSHOT.jar!/:3.4.0-SNAPSHOT] at com.netflix.conductor.core.reconciliation.WorkflowSweeper$$FastClassBySpringCGLIB$$f994448e.invoke(<generated>) ~[conductor-core-3.4.0-SNAPSHOT.jar!/:3.4.0-SNAPSHOT] at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218) ~[conductor-es7-persistence-3.4.0-SNAPSHOT.jar!/:3.4.0-SNAPSHOT] at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:779) ~[conductor-es7-persistence-3.4.0-SNAPSHOT.jar!/:3.4.0-SNAPSHOT] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163) ~[conductor-es7-persistence-3.4.0-SNAPSHOT.jar!/:3.4.0-SNAPSHOT] at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:750) ~[conductor-es7-persistence-3.4.0-SNAPSHOT.jar!/:3.4.0-SNAPSHOT] at datadog.trace.instrumentation.springscheduling.SpannedMethodInvocation.invokeWithSpan(SpannedMethodInvocation.java:50) ~[?:?] at datadog.trace.instrumentation.springscheduling.SpannedMethodInvocation.invokeWithContinuation(SpannedMethodInvocation.java:42) ~[?:?] at datadog.trace.instrumentation.springscheduling.SpannedMethodInvocation.proceed(SpannedMethodInvocation.java:36) ~[?:?] at org.springframework.aop.interceptor.AsyncExecutionInterceptor.lambda$invoke$0(AsyncExecutionInterceptor.java:115) ~[conductor-es7-persistence-3.4.0-SNAPSHOT.jar!/:3.4.0-SNAPSHOT] at org.springframework.aop.interceptor.AsyncExecutionAspectSupport.lambda$doSubmit$3(AsyncExecutionAspectSupport.java:276) ~[conductor-es7-persistence-3.4.0-SNAPSHOT.jar!/:3.4.0-SNAPSHOT] at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1700) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?] at java.lang.Thread.run(Thread.java:829) [?:?]

[BradenEads]

Hi!

Based on the logs you provided, it appears that there is a NullPointerException occurring when trying to access the workflow definition. The error is thrown during the sweeping process, which is trying to reconcile running workflows.

Possible reasons for this issue may include:

1. The workflow definition is missing or not properly registered in the database.
2. There could be a mismatch between the workflow definition version in the database and the version being used by the application.
3. Data corruption in the MySQL database.

Here are some steps to troubleshoot and resolve the issue:

1. Check if the workflow definition is registered properly in Conductor. You can use Conductor's API or UI to fetch the workflow definitions and verify if the affected workflow is present with the correct details.
2. Make sure that the version of the workflow definition in the database matches the version expected by your application. If there's a mismatch, update the version accordingly.
3. Verify the integrity of the data in the MySQL database. You can use tools like mysqlcheck to check and repair any corruption in the database.
4. If you have recently upgraded Conductor, double-check the migration steps to ensure that all required changes have been applied correctly.

If the issue still persists, consider enabling more detailed logging in Conductor to get additional insights into the issue. You can increase the log level to DEBUG or TRACE for the com.netflix.conductor package in your logging configuration.

If none of these steps resolve the issue, please provide more information about your setup, including any customizations or additional configurations, to help further diagnose the problem.