> For the complete documentation index, see [llms.txt](https://studio-docs.japan-ai.co.jp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studio-docs.japan-ai.co.jp/en/troubleshooting/workflow-not-starting-or-failing.md).

# A Workflow Does Not Start or Fails

This page provides steps to isolate when the Workflow cannot be run manually, does not start as scheduled for an event or task, or fails after starting. Target users are creators and operators. First, distinguish between testing drafts, manual execution of published workflows, triggers, and schedules managed with "tasks." Changes to the draft will not be reflected in regular usage, triggers, or scheduled executions until you publish it.

## Related articles

* [Test Workflow Draft](/en/build-workflows-and-automatic-execution/test-workflow-drafts.md)
* [Publish Workflow](/en/build-workflows-and-automatic-execution/publish-workflow.md)
* [Set Workflow trigger](/en/build-workflows-and-automatic-execution/configure-workflow-triggers.md)
* [Debug with Workflow execution history](/en/build-workflows-and-automatic-execution/debug-workflow-run-history.md)
* [Configure task scheduler](/en/build-workflows-and-automatic-execution/configure-task-scheduler.md)
* [Respond to connection expiry/change of person in charge](/en/administration-and-operations/handle-expired-connections-and-owner-changes.md)
* [Change/stop/inherit periodic execution](/en/administration-and-operations/change-stop-handover-scheduled-runs.md)
* [Set execution result notification](/en/administration-and-operations/configure-run-result-notifications.md)
* [Collect information necessary for inquiries](/en/troubleshooting/collect-info-for-support.md)

## Before you start

* Identify which method to start with. The confirmation location differs for tests on the editing screen, manual execution by users, event triggers, and schedules managed with "tasks".
* Record the target organization/Project/Workflow name, publication status, start node, date and time of occurrence, executor or event.
* Workflows that send emails, create/update objects, and update external services may have already been processed halfway even when they fail. Do not repeatedly "start execution" or re-execute without knowing the cause.
* Tests should be performed with configurations that do not require external updates as much as possible, or with permitted test connection destinations and data.

> Not receiving notifications is not the same as not starting Workflow. First, check whether there is a record in the "execution history" or "execution history" of the task, and then separate the execution, results, and notifications.

## Check first

* [ ] Checked whether the target was a draft or "published" and how to start.
* [ ] "Temporarily save" the modified draft and "publish" it if necessary.
* [ ] Checked the start node, required inputs, variable references, and unconnected/unset nodes.
* [ ] For triggers, check the event conditions, connection, and public status; for schedules, check the valid status, next execution, and creator.
* [ ] Checked the status, result, step, and first node of the target execution in the execution history.
* [ ] Confirmed the impact of external transmission and record duplication due to re-execution

## Isolation by symptoms

| Symptoms/Displayed Messages                                                                      | Main Causes                                                                                                                                                                                        | Checks/Treatments                                                                                                                                                                                                                                                     | Detailed Articles                                                                                                                                                                                                                              |
| ------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| "This workflow cannot be executed because it is disabled"                                        | The workflow is disabled or the target is confused                                                                                                                                                 | Check the status of the target workflow. Simply reorganizing the draft will not change the published version. After testing the necessary modifications, "Publish" and check "Published" and the actual execution results.                                            | [Publish Workflow](/en/build-workflows-and-automatic-execution/publish-workflow.md)                                                                                                                                                            |
| Does not start with a trigger/"Please publish the workflow to enable the trigger"                | The start node/event condition is inappropriate as it is in the draft, and the linkage has expired. For triggers such as Gmail/Outlook, it is also necessary that the Workflow has been published. | Publish the target Workflow and check the start node type, target, filtering conditions, and connection with external services. Executing a test alone will not confirm activation in a real event.                                                                   | [Set Workflow trigger](/en/build-workflows-and-automatic-execution/configure-workflow-triggers.md)                                                                                                                                             |
| "Input required" or "Unable to execute the workflow. Please correct the following:"              | Required input is empty, node setting/variable reference/connection is incorrect                                                                                                                   | Check the input on the execution screen, the start node, the displayed node name and reason. Correct any indications such as "input variable is required" or "data set is required" at the relevant node and save it temporarily.                                     | [Test Workflow draft](/en/build-workflows-and-automatic-execution/test-workflow-drafts.md)                                                                                                                                                     |
| "Execution failed"                                                                               | Failed in node execution, input value, variable, external service, or connection                                                                                                                   | Open "Results" and "Steps" for the target execution and follow the inputs and outputs in order from the start node. Targets correction not only for nodes in error, but also for nodes whose values ​​were initially different from expected.                         | [Debug with Workflow execution history](/en/build-workflows-and-automatic-execution/debug-workflow-run-history.md)                                                                                                                             |
| Execution is slow or "timed out"                                                                 | External services, processing volume, node settings/wait, connection destination response                                                                                                          | Check the elapsed time and failed steps in the execution history, and do not start the same execution continuously. Check the node input, number of targets, and restrictions on the external service side, and divide the process or review the design if necessary. | [Debug with Workflow execution history](/en/build-workflows-and-automatic-execution/debug-workflow-run-history.md) / [Workflow/Automatic execution specifications/limitations](/en/specifications-and-limits/workflow-and-automation-specs.md) |
| Error when receiving Gmail/Outlook triggered email                                               | Expired connection, different account, failed linkage settings after publication                                                                                                                   | Check the connection status, authentication account, permissions on the external service side, and publication status in order. Re-authentication is performed after checking the existing connection account.                                                        | [Respond to connection expiration and change of person in charge](/en/administration-and-operations/handle-expired-connections-and-owner-changes.md)                                                                                           |
| The schedule does not run / "The task was not executed because it is disabled"                   | The task is disabled, stopped in the organization, or the next execution/end date is inappropriate                                                                                                 | Check whether the status is "Active" or "Stopped in the organization" in "Using" for "Task" and whether the "Next execution" and end date of the target task are as intended. Check the time zone settings and display saved in the task.                             | [Set the task scheduler](/en/build-workflows-and-automatic-execution/configure-task-scheduler.md) / [Change, stop, or take over periodic execution](/en/administration-and-operations/change-stop-handover-scheduled-runs.md)                  |
| "The task was not executed because the creator of the task is not a member of the organization." | The execution conditions are not met due to the creator's transfer or retirement, etc.                                                                                                             | Instead of activating the old task, the successor checks the execution content, connections, notifications, and schedule, creates a new task, and confirms the first execution.                                                                                       | [Change/stop/take over periodic execution](/en/administration-and-operations/change-stop-handover-scheduled-runs.md)                                                                                                                           |
| Execution is successful but notification is not received                                         | Notification destination settings, recipient authority, webhook/token expiration                                                                                                                   | First check the execution results of the Workflow, then check the status of the task's "notification destination", destination, and notification destination service side. Do not paste the destination URL or token into the inquiry.                                | [Set execution result notification](/en/administration-and-operations/configure-run-result-notifications.md)                                                                                                                                   |

## 1. Check the boot paths separately

1. If you tried from the editing screen, check the "execution history" of the draft. This is for testing before publication.
2. If a user/trigger is activated after publishing, check the execution log of the target workflow. If you can use the organization's "task", check the target workflow in "Create" and open the available "execution history". Test runs on the edit screen are not displayed here.
3. For event triggers, check that the Workflow is 'published' and that the event conditions and connections on the start node are correct. We will confirm once at the actual event after publication.
4. For regular execution, open the target task from `Used'' under` Tasks'' and check the status, \`\`Next execution'', end date, and execution history. Even if you edit a Workflow, only the published version will be executed.

## 2. Check input and settings before publishing

If this fails, record the node name and reason for the message that appears, and check the following steps:

1. Check the required items for manual input and the input format such as URL, JSON, and numerical values.
2. Verify that the start node matches your expected start method.
3. Check the "Checklist" for unconnected nodes, incorrect settings, and required prompts, models, variables, Datasets, and tools.
4. Check that the referenced variable does not point to an output that has been deleted or renamed, and that the type matches the value for each branch.
5. After making corrections, "temporarily save" and test typical inputs and inputs that result in errors. To reflect it in normal use or automatic startup, "publish" it after testing.

## 3. Check the execution history for failed nodes

Check the status, error, and elapsed time under "Results" in the execution details, and view the inputs and outputs of each node in order from the start node under "Steps." Empty input, unexpected branches, mismatched output formats, and connection/authority/destination errors are identified. Success is not a guarantee that the business results are correct, so please also check the destination, update destination, and final output. Even if a failed event execution shows "Rerun", it will run with the saved inputs. If writing to Object, etc. was completed before the failure, there is a possibility that it will be duplicated when re-executed. Check the cause, existing records, and external sending status before executing. If manual execution fails, check the input from the normal execution screen and try again.

> Even if the connection appears to be "authenticated", it will fail if the permissions to the target folder, destination, record, or restrictions on the external service side change. Don't assume that the connection is the only cause, first check the failed nodes in the execution history and the input/output.

## Before consulting with administrator/support

Except for confidential information, email body, tokens, webhook URLs, and personal information, we record the following: Workflow name and organization/Project, start method, publication status, date and time of occurrence, execution ID or task name, status, display message, failure node, shareable summary of inputs and outputs, connection status, external processing that has been executed, whether or not it will be re-executed, and confirmed actions. When saving execution data in JSON, it includes input and output, so limit where it can be saved and who it can be shared with. For more information, please refer to [Collect information required for inquiries](/en/troubleshooting/collect-info-for-support.md).

## Read next article

* [Debug with Workflow execution history](/en/build-workflows-and-automatic-execution/debug-workflow-run-history.md)
* [Set Workflow trigger](/en/build-workflows-and-automatic-execution/configure-workflow-triggers.md)
* [Configure task scheduler](/en/build-workflows-and-automatic-execution/configure-task-scheduler.md)
* [Respond to connection expiry/change of person in charge](/en/administration-and-operations/handle-expired-connections-and-owner-changes.md)
* [Change/stop/inherit periodic execution](/en/administration-and-operations/change-stop-handover-scheduled-runs.md)
* [Collect information necessary for inquiries](/en/troubleshooting/collect-info-for-support.md)
