How to turn off the Lightning Workflow

You uninstall Lightning Workflow module just like any other Drupal module:

2. Go to admin/modules/uninstall
3. Recursively disable all of Lightning Workflow's dependencies
4. Disable Lightning Workflow

Note that Lightning Workflow currently depends on Workbench Moderation which might have issues with being uninstalled:
#2762777: Cannot uninstall workbench moderation module

Same here, I uninstalled Lightning Workbench and when I try to reinstall it, I get the following error:

Unable to install Lightning Workflow, core.entity_form_display.scheduled_update.multiple_node_embargo.default, core.entity_form_display.scheduled_update.node_embargo.default, field.field.scheduled_update.node_embargo.field_moderation_state, field.storage.node.scheduled_update, field.storage.scheduled_update.field_moderation_state, scheduled_updates.scheduled_update_type.multiple_node_embargo, scheduled_updates.scheduled_update_type.node_embargo, views.view.moderation_history already exist in active configuration.

I'm confused why this issue was closed. I can duplicate the issues detailed above in that I can uninstall the Lightning Workflow and then when I reinstall I get the error:

"Unable to install Lightning Workflow, views.view.moderation_history already exists in active configuration."

If this is being worked on elsewhere, it would be a lot more helpful to cross link to that issue.

There is clearly a number of use cases where you'd want to disable this workflow and the side effects of doing so is pretty rough right now. For example, the main body field of the basic page is nuked.

Hi @justinlevi. You cannot reinstall any module that provides config unless you first delete that config from active configuration. Try installing the core Tracker module, uninstalling, and installing it again. You will get the same error. This is by design in core.

You can use Drush or Drupal Console to delete the configuration if you want to reinstall the module.
E.g.: https://docs.drupalconsole.com/en/commands/config-delete.html

Thanks for the info, that's very helpful.

Do you know if there is any issue open regarding this being broken UX in core? This definitely comes off as broken to the end user.

@justinlevi I do not. I know quite a few have been confused by it though. The exception is actually quite informative, but if you don't have a background in D8 config, I can see where it might be confusing. Maybe just a little extra info in the exception message would help. Something like:

Unable to install [MODULE_NAME] because [MODULE_NAME] provides the following configuration entities [...] which already exist in active configuration. You must delete that configuration, which may have adverse affects, in order to install [MODULE_NAME].

A quick search didn't turn up anything. Feel free to update the Issue Summary and move this to the Core issue queue if you like.