Skip to Main Content
Categories Workflow
Created by Guest
Created on Sep 17, 2026

Workflow error handling, prevent hanging and allow edits

How:

  1. Create a data model with a field.

    1. In control center update a model to add a new field called 'ToBeDeleted' with data type String.

  2. Create a Workflow to assign a value to that field in the model based on some trigger

    1. Create a visual workflow with some trigger that includes an entity automation that sets the value of the new field 'ToBeDeleted' (can be set to a static value).

  3. Remove the field created in Step 1

    1. In control center update the model from step 1 to remove the field called 'ToBeDeleted'.

  4. Trigger the workflow created in step 2

    1. Click into View in Progress on the workflow.

    2. Observe that the workflow did start.

    3. Observe that the workflow does not complete the entity automation step, but get stuck in an in progress state.

    4. Click 'Switch to Edit' to edit the workflow.

    5. attempt to edit the Entity automation step

    6. Observe that the UI reports an error: Error TypeError: Cannot read properties of undefined (reading 'datatype')

At this point the only ways to restore functionality is to recreate the field that was deleted called 'ToBeDeleted' or to remove the entity automation step that was attempting to set the value of the field 'ToBeDeleted'
When removing the entity automation step all items in progress in the workflow on that current step are removed. They are not added to the history of the workflow.

Why:

I would expect the workflow to report an error. I would expect that the workflow handle the situation more gracefully allowing a user to see what field is missing.
Alternatively I would expect that you cannot remove a field from a data model that was in use by workflows.

For Who:

People who manage workflows and data models

Impact:

Any items that are in the workflow are disrupted and potentially lost in the process. That workflow cannot continue to progress regardless of user's input unless the data model is restored

Additional context:

This has occurred in our system with less than 6 months in the product.

  • Attach files