Skip to main content

Automations

Automations run instructions with an agent manually, periodically, or on a specific date. The section contains the Tasks and Execution history tabs.

Creating a task​

Select New automation to open the task configuration form.

Information​

Define the name, description, state, and agent. The agent provides its instructions, sources, and tool policies. If you do not select an agent, GESCON uses the default agent (All your documents).

Schedule​

Choose one of these modes:

  • On demand: runs only when started manually.
  • Recurring: uses the frequency and time builder.
  • Scheduled: runs once on the selected date and time.

Check the displayed time zone, especially for distributed teams.

Configuration​

This part of the form lets you select integrations and enable web search, deep research, expert mode, and persistent files.

Enabled options

Only options enabled for the selected agent are shown. If an option needed by the automation is missing, check the agent configuration.

Instructions​

Describe the task in Markdown, including the expected format, data period, and success criteria. The limit is 32,768 characters.

Detailed instructions

Tasks run without information beyond what you provide here, so ambiguous tasks may return incomplete or incorrect results. Specify the steps the agent should follow so the task runs as intended.

Output​

Deliver the result by Chat, Notice, or Email. For notices and email, provide the recipients. You can also configure the retry policy after errors, from 0 to 10 retries.

Managing tasks​

From an automation's menu, you can run, edit, activate or deactivate, and delete it. Deactivation preserves the configuration but prevents new scheduled runs. Confirm before deleting, because the action cannot be undone from the interface.

Execution history​

This tab lets you search and filter by task, state, or date. Each row shows the result of a run and its retries.

The details may include:

  • Generated result.
  • Operational reasoning and tools used.
  • Execution and delivery states.
  • Error information, if applicable.
Execution and delivery

A task may finish successfully and then fail while delivering the result, for example because of an invalid email address. Review both states.

Recommendations​

  • Start on demand and activate the schedule after validating the result.
  • Use specific instructions and review executions periodically to prevent errors.
  • Review the first runs after changing an agent, source, or connector.