> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/generic/date-operations/get-current-day.md).

# Get Current Day

This is a pre-built Action located under the **@Generic Element**. The functionality of this Action in Avo Assure is to fetch the current system date based on the specified format. The extracted day is stored in the given dynamic variable for further use during test execution.

## **Syntax**

**Input Value**: `N/A`

| Argument | Description    |
| -------- | -------------- |
| N/A      | Not Applicable |

**Output Value**: `<Dynamic Variable>;<Dynamic Variable>(Optional)`

| Argument                                 | Description                                                       |
| ---------------------------------------- | ----------------------------------------------------------------- |
| <p>\<Dynamic Variable><br>(Required)</p> | This dynamic variable stores the current day from the system.     |
| <p>\<Dynamic Variable><br>(Optional)</p> | This dynamic variable stores the status as **True** or **False**. |

### **Example:** Retrieving the Current Day of the Week

In this example, we explain how to get the current system day based on the system’s date and time.

* **Action**: Get Current Day
* **Input Value**: N/A
  * This action does not require any input value in the **Input Value** column. It automatically retrieves the current day of the week from the system.
* **Output Value**: {CurrentDay}
  * The retrieved system day (Monday) is stored in this **{CurrentDay}** dynamic variable.
  * If a second output variable is provided, then action returns the status as **True** or **False**:
    * **True**: If the current day is successfully retrieved.
    * **False**: If the retrieval fails due to a system issue.
* **Logical Explanation**: The **Get Current Day** action retrieves the current system day (Monday) and stores it in the **{CurrentDay}** variable.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FQUdcsi6eZktfZLFZgo2t%2Fimage.png?alt=media&amp;token=efa41fda-605f-4c98-8fee-da746a39c736" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avoautomation.com/avo-assure/actions/generic/date-operations/get-current-day.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.