Common questions and solutions for setting up and running Workflows are answered below.
What to Do When a Workflow Does Not Fire
Most cases where a Workflow does not respond come down to a missing setting in its status, trigger, or action. Check the following items in order.
Points to Check
| Check item | Details |
|---|---|
| Status | Whether the Workflow's status is set to "Active". It will not respond to triggers while in the "Draft" or "Paused" status |
| Trigger | Whether the trigger type and conditions match the event you expect to start it |
| Action | Whether every required field for each action, such as message content or tags, has been filled in |
| Target LINE account | Whether the LINE account that the Workflow applies to has been selected |
Steps After Correcting a Setting
Once you have corrected a setting, always click "Save" and then click "Start". Changes will not take effect unless you save. After starting, perform the action that actually serves as the trigger and confirm that the Workflow behaves as expected.
Can I Run Multiple Workflows From the Same Event?
The behavior depends on the event. Some triggers, such as adding a friend, can fire multiple Workflows at the same time, while others have their execution controlled by priority.
Example of Firing at the Same Time
If you set up a Workflow that sends a welcome message and a separate Workflow that sends a survey, both using "Friend added" as the trigger, both will run when a friend is added. Splitting Workflows by purpose makes it easier to edit or pause each one individually later on.
When Execution Is Controlled by Priority
You can set a "Priority" on message-received triggers. The smaller the number, the higher the priority, and when a higher-priority trigger matches the conditions, the Workflows for lower-priority triggers do not run. Triggers with the same priority run in parallel.
Can I Check a Workflow's Execution History?
In the Workflow editing screen, click "Execution History" to review the execution status and the result of each action.
What the Execution History Shows
| Item | Details |
|---|---|
| Statistics | Total executions, successes, failures, average processing time, and last execution date and time |
| Filtering | Switch the view by All / Failed / Pending / Running / Succeeded |
| Details of each execution | Select an execution to review the status and input/output of each action |
When you click the action history for an execution, you are taken to the corresponding node on the canvas. This lets you visually trace which step it stopped at while you review it.
Can I Pause a Workflow?
In the editing screen, click "Pause" to temporarily pause the Workflow.
How Pausing and Resuming Behave
When you set a Workflow to paused, it stops responding to triggers. To resume it, click "Start".
Triggers that occur while the Workflow is paused are not processed. In addition, messages that have already begun being delivered or processing that is being delayed may be interrupted partway through by the pause. Because this can affect the timing of a broadcast, take care when stopping a Workflow that is running.
Greetings Arrive Twice for Friends Added via QR Code
Turning on "Exclude via QR Code" on the friend-added trigger prevents the duplication.
Why the Duplication Happens
When someone scans a QR Code and becomes a friend, both the "Friend added" and "QR Code scanned" triggers fire. If you have a Workflow set up for each one, the message arrives twice.
Steps to Set Up the Exclusion
- Open the Workflow for the friend-added trigger
- Click the trigger node (Friend added) to display the sidebar
- Turn on "Exclude via QR Code"
- Click "Save"
When you turn this setting on, the friend-added trigger's Workflow does not fire for friends added via QR Code, and only the QR Code trigger's Workflow runs.