# Workflow Application: Assembly: The assembly system action started but did not complete successfully

**URL:** <https://discuss.workflowgen.com/t/workflow-application-assembly-the-assembly-system-action-started-but-did-not-complete-successfully/484>\
**Category:** Workflow Applications\
**Created:** [January 12, 2015, 6:07pm UTC](https://discuss.workflowgen.com/t/workflow-application-assembly-the-assembly-system-action-started-but-did-not-complete-successfully/484 "2015-01-12T18:07:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![wfg-admin](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.workflowgen.com/wfg-admin/32/714_2.png) [@wfg-admin](https://discuss.workflowgen.com/u/wfg-admin)\
**Post date:** [January 12, 2015, 6:07pm UTC](https://discuss.workflowgen.com/t/workflow-application-assembly-the-assembly-system-action-started-but-did-not-complete-successfully/484/1 "2015-01-12T18:07:00Z")

</div>

When completing or cancelling an action using one of the methods listed below, and the next action is an assembly system action, the system action can start but not complete successfully.

- Using Remote Approval to complete the action
- Using the Web Service API to complete or raise an exception on the action
- Using the WorkflowGen Engine service to cancel the action on overdue

**Solution**

Your assembly DLL must be deployed in the following folders:

- `\wfgen\bin`

- `\wfgen\ws\bin`

- `DRIVE:\Program Files\Advantys\WorkflowGen\Services\bin`

**Important:** You must stop the WorkflowGen Engine service before copying your assembly DLL into the bin folder.