# Assertion step ### ![](https://543770944-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-olTwg7hZbNL0ezRh2%2F-M-olXfbMrXfFk9mTi7I%2Fhelp_root_applications_workflow_icons_assertion.png?alt=media\&token=3ca7d9a6-b5ff-4e82-98e2-87d3c9714a49) Assertion steps are used to perform "sanity checks" on variables in the workflow. An assertion step consists of one or many conditions (see [Decision steps](https://home.novacuraflow.com/Help/latest/?designer_applications_workflow_decision_step)) and an error message to be shown to the operator in case the conditions are satisfied. If an assertion step generates an error message, the operator is automatically returned to the most recent user step. ![](https://543770944-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-olTwg7hZbNL0ezRh2%2F-M-olaKvLoHhCMQnAbQT%2Fhelp_root_applications_workflow_assertion_example.png?alt=media\&token=1b98310a-980d-479e-9246-8643b385486e) --- # Agent Instructions: 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: ``` GET https://help.novacuraflow.com/6.11/development/flow-studio/applications/workflow/assertion-step.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.