> For the complete documentation index, see [llms.txt](https://docs.elkyc.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elkyc.com/home/build-verification-flows/workflow-drafts.md).

# Workflow Drafts

The Workflow Builder includes a convenient auto-save feature that ensures your work is not lost if you forget to save manually.

If you create or modify a workflow but do not click the `Save` button before closing the page, the workflow will automatically be saved as a draft. This functionality helps prevent data loss and allows you to continue your work seamlessly at a later time.

* To continue working on a draft workflow, simply navigate to your list of workflows and locate the ones marked as "Draft.”
* Click on the draft workflow to open it and continue editing from where you left off.
* Once you have completed your changes, click the `Save` button to finalize the workflow.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.elkyc.com/home/build-verification-flows/workflow-drafts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.