---
title: "My request won’t flow to the next task"
canonical_url: "https://www.nutrient.io/guides/workflow-automation/troubleshooting/my-request-wont-flow-to-the-next-task/"
md_url: "https://www.nutrient.io/guides/workflow-automation/troubleshooting/my-request-wont-flow-to-the-next-task.md"
last_updated: "2026-05-15T19:10:05.124Z"
description: "Troubleshoot process flow issues in Nutrient Workflow Automation. Covers invalid rules, task configuration errors, recipient assignment issues, and incomplete start rules."
---

# My request won’t flow to the next task

When troubleshooting a process that doesn’t flow to the next task, focus on general task configuration, and then analyze the start and recipient rules of tasks following the last completed task. Nutrient Workflow Automation typically stops a process for the following reasons.

1. **Invalid rules on the task**

   **Resolution** — Check the **Process Flow** canvas for a yellow warning icon on the task. If the icon is present and hovering the pointer over the task shows **Rules valid: false**, the task references deleted transitions or removed tasks. Open **Configuration** > **Configure Rules** for the task and correct or remove the invalid rules. Refer to [invalid rules detection](https://www.nutrient.io/guides/workflow-automation/admin-guide/processes/tasks/task-menu/configuration/configure-rules-editor.md#invalid-rules-detection) for more information.

2. **General task configuration issues**

   **Resolution** — Ensure you’ve fully configured all tasks following the completed task in the request.

3. **Recipient assignment failures**

   **Resolution** — A user-interaction task, such as a form, won’t start if it can’t identify a valid recipient. This occurs if dynamic assigner tasks fail to provide a valid user, or if you’ve assigned the task to a deactivated user. To resolve this, audit your recipient rules to ensure they account for all possible scenarios, and verify that assigned users are active in the system.

4. **Incomplete or opposing start rules**

   **Resolution** — The workflow stops if rules don’t cover every possible selection, which is common when a form question enables multiple answers like a checkbox. For example, if a user selects both “Laptop” and “Monitor,” an “Is” operator might fail because the system stores the data as a combined string. To resolve this, use the **Contains** operator in your rules rather than **Is** to account for multiple values.
---

## Related pages

- [Improve your PDF exports with streamlined forms](/guides/workflow-automation/troubleshooting/when-i-export-to-pdf-some-fields-are-blank-even-though-the-formatted-view-shows-those-boxes-as-completed.md)
- [Optimize your notification settings for Workflow Automation](/guides/workflow-automation/troubleshooting/error-in-the-custom-notification-for-this-email-please-notify-the-process-owner.md)
- [Understanding notifications in Workflow Automation](/guides/workflow-automation/troubleshooting/when-i-change-my-process-to-a-testing-or-production-publish-status-some-notifications-are-not-being-sent-to-task-recipients.md)
- [Streamline task assignments with upcoming features](/guides/workflow-automation/troubleshooting/integrify-will-not-allow-me-to-assign-a-whole-group-to-an-initialized-task.md)
- [Ensure seamless command execution in automation](/guides/workflow-automation/troubleshooting/when-i-run-a-command-directly-on-the-server-it-works-fine-however-when-run-from-the-command-line-task-type-it-fails.md)
- [Preventing email notifications from being blocked](/guides/workflow-automation/troubleshooting/why-are-notifications-from-our-cloud-instance-being-dropped-blocked-or-marked-as-spam.md)
- [Configure your email server for scheduled reports](/guides/workflow-automation/troubleshooting/why-am-i-not-receiving-scheduled-reports.md)