Work Order System Status sets "Closed-Canceled" throws Error "Workflow must be Published"

(0) Share

Report

Posted on by Bilal Islam

when user set Work Orde system status field to "Closed-Canceled", then system throws exception

2185.tempsnip.png

In log file

Exception Message: Workflow must be in Published state.

ErrorCode: -2147220891
HexErrorCode: 0x80040265

ErrorDetails:
ApiExceptionSourceKey: Plugin/Microsoft.Crm.ObjectModel.WorkflowService
ApiStepKey: 46f6cf4c-14ae-4f1e-98a1-eae99a37e95c
ApiDepthKey: 2
ApiActivityIdKey: 3984c89d-b4d0-4f9c-b314-d1a86345cb15
ApiPluginSolutionNameKey: System
ApiStepSolutionNameKey: System
ApiExceptionCategory: ClientError
ApiExceptionMesageName: ExecuteUnpublishedWorkflow
ApiExceptionHttpStatusCode: 400
OperationStatus: 0
SubErrorCode: -2146233088

TraceText:
[Microsoft.Dynamics.FieldService: Microsoft.Dynamics.FieldService.FieldServicePlugin]
[81819e14-09c5-48d4-bf9d-f1147df5f501: Field Service: Update (post-operation) for msdyn_workorder]

[Microsoft.Crm.ObjectModel: Microsoft.Crm.Extensibility.InternalOperationPlugin]
[46f6cf4c-14ae-4f1e-98a1-eae99a37e95c: ExecuteWorkflowWithInputArguments]

Activity Id: cae17c64-36ac-4ddc-b880-623bf5000c95

Any one have idea how to fix that issue?

Many Thanks

All responses (2)

Answers (1)

Bilal Islam 80 on at

Like (0)

Report

RE: Work Order System Status sets "Closed-Canceled" throws Error "Workflow must be Published"

Thank you Leah Ju,

it was because of one workflow triggers as child flow in another custom action

and this custom action triggers in Plugin on System Status field change.

it was issue reason.

When I reactivated it, it works.

Again Thank you Leah Ju
Verified answer

Community Member Microsoft Employee on at

Like (1)

Report

RE: Work Order System Status sets "Closed-Canceled" throws Error "Workflow must be Published"

Hi Bilal,

The immediate thought was to check all the workflow associated to work order and see if they all are published.

You can Go Settings > Process

Make sure status is active.

Then I'd suggest Deactivating and then Reactivating the workflow and see if the issue still occurs.

Regards,

Leah Ju

Please mark as verified if the answer is helpful. Welcome to join hot discussions in Dynamics 365 Forums.