Testing
- Start a test task for every branch of your workflow and work through it to the end.
- Through the API, add mode=test to start a task named "[Test task]", which keeps tests out of your normal task names.
- Check your documents in the browser before relying on them in a workflow.
- Delete test tasks when you've finished.
An item doesn't appear
Check, in this order:
- The connection is two-sided. The earlier item has ---outcome: (or ---filterN|outcome:) naming this item, and this item has ---depends_on: naming the earlier one.
- IDs match exactly. IDs are case-sensitive, and a typo breaks the link silently.
- The earlier item is done. Items are only "done" once completed or skipped.
- A filter matched. If the earlier item has filters, its plain ---outcome is ignored, and nothing follows if no filter matches. For questions, the filter must use the exact answer text.
- The earlier item is itself showing. If it never appeared, nothing after it will.
- Nothing is blocking it. A ---block:true item or a Blocker above it holds it back until earlier items are done.
A document won't lock
A document can't be locked while it contains a variable with no value and no fallback text. Give the variable a value through ---pass_variables, or add fallback text in the template: {{variable_name|Not applicable}}.
An email or SMS didn't send
- Check the ---to address or number is valid once variables are filled in. Separate several addresses with commas.
- Check variables in ---to have values at that point in the task.
A variable shows as blank or as a line
A variable with no value shows as a blank line (____________) in documents. Check the spelling, check the item that sets it has been answered, and remember that document variables need a prefix: {{alias:variable}}.
A payload fails
Open the task item to see the response code and output. Check the URL starts with https://, the content type matches what the receiving system expects, and any {{variables}} in the payload have values.