Runs and triggers

Once an automation is ready, day-to-day work comes down to two questions: what has run? and when does the robot run on its own? The “Execuções” (Runs) tab answers the first: it is the history of every run, with its date, origin, status and machine. The “Gatilhos” (Triggers) screen answers the second: there you set when your automations start running on this computer, at a set time or when new items reach a queue.

And if a run breaks with a technical error, the Curador, Curator's self-healing agent, takes over right away when it is turned on for that automation: it looks at the screen, decides and fixes.

Start with what you want to do

• See what has runEvery run is in the “Lista de Execuções” (run list).
• Understand a failureEach run's origin, status and machine.
• Keep the historyFilter by project, search and export.
• Run at a set timeCreate a time trigger.
• Run when work arrivesNew items in a queue start the automation.
• Follow from anywhereMachines, triggers and runs in the web portal.

Run list

Every run of an automation is recorded in the “Execuções” (Runs) tab, the second tab at the top of the window. To check whether the robot ran and how it ended:

1. Open the “Execuções” tab It sits at the top, between “Automação” (Automation) and “Filas” (Queues).
2. Stay on “Lista de Execuções” It is the first of two sub-tabs. The other one, “Fila de Execução” (run queue), sits right next to it.
3. Pick the project In “Projeto:” (project), leave “Todos” (all) to see everything, or pick one automation to see only its runs.
4. Read the row Each row is one run: when it ran, how it started, how it ended and on which machine. See what each column says.
5. Click “Atualizar” if needed A run just finished and isn't there yet? “Atualizar” (refresh) reloads the list.

What each column says

Every row has the same eight columns. Below, the list redrawn with made-up examples so it reads well on any screen:

Redrawn example with made-up names. The columns, buttons and labels are the ones on the real screen.

Below the list, “Mostrando 1-1 de 1” (showing 1-1 of 1) tells you which rows are on screen. To change pages, use “<<”, “< Anterior” (previous), “Próximo >” (next) and “>>”; “Página 1 de N” (page 1 of N) sits in the middle.

Run queue

Next to “Lista de Execuções” is the “Fila de Execução” (run queue) sub-tab. The list shows what has already run; the run queue holds the runs still waiting for their turn on this machine.

Don't mix it up with the “Filas” tab

Search and export

The bar above the list helps you find a run and export the history:

What a trigger is

A trigger is the rule that makes an automation start on its own, without anyone clicking “▶ Executar” (Run). The “Gatilhos” (Triggers) screen puts it in one sentence: “Set when your automations start running on this computer.”

There are two kinds, and the counters at the top of the screen show how many of each you have:

Note the words “on this computer”: the trigger makes the automation run here, on this machine. Every run a trigger starts shows up in the run list with the origin “Gatilho” (trigger).

Time trigger

The automation starts on its own at the time you set. It is the right kind for routines with a fixed time: the check that must be done before the team arrives, the data collection that runs while the computer is free.

It fits two of the REFRAMEWORK templates:

• “Automação simples” (simple automation), which works through the rows of a spreadsheet, with no queue.
• “Dispatcher”, which collects the data and queues the items for the Performers. The template's own diagram starts at “Início (agendado/cron)” (start, scheduled/cron).

On the “Gatilhos” screen, the “N por horário” counter shows how many time triggers there are.

Queue trigger

Here, the work that arrives is what starts things: you use the new items in a queue to start an automation. No need to guess a time. New items arrive, the automation starts.

It is the natural partner of the “Performer”, the template that consumes the queue and processes the items; several Performers can run in parallel. One way to combine them:

The Dispatcher runs on schedule and feeds the queue; the new items start the Performer.

On the “Gatilhos” screen, the “N por fila” counter shows how many queue triggers there are. To set up the pair, see Dispatcher and Performer; to create and follow the queue, see Queues.

Create a trigger

Before you let the robot run on its own, a quick check pays off. When nobody is watching, every detail you got right beforehand counts.

Before you create it

• Run the automation once with “▶ Executar” and check the result in the run list.
• Changed something? Check that part with a snippet test, which uses the same Python, adapter and connection as “Executar”.
• Queue trigger? The queue has to exist. Create it in the “Filas” tab, with “+ Nova fila” (new queue).
• Does the automation use Chrome? In “Configurações” → “Google Chrome”, check that the extension shows “Habilitada no Chrome” (enabled in Chrome), or use “Verificar instalação” (check installation).
• Turn the Curador on for that automation. See below why.

Now, the trigger

1. Click “+ Criar gatilho” It is the green button (create trigger) in the top right corner of the “Gatilhos” screen. While the screen is still empty, the “Criar gatilho” button in the middle works too.
2. Say when the automation starts A trigger links an automation to a time or to the new items in a queue. Follow the creation window.
3. Check the counters At the top, “N ativos” (active), “N por horário” (by time) and “N por fila” (by queue) show how many triggers are active and how many there are of each kind.
4. Follow it in “Execuções” When the trigger fires, the run shows up in the list with the origin “Gatilho” (trigger).

Find triggers

Once you have many triggers, the bar below the counters helps you find the one you want:

For a quick answer, look at the counters: “N ativos” (N active) tells you how many triggers are active right now.

From the web portal

You don't have to be at the computer to know what ran. In the PYE Tech web portal, at pyetech.com.br/Portal, you sign in with your account and follow the workspace from your browser. As Curator's “Sobre” (About) screen puts it: “The account, the workspace and the run history exist so you can sign in, work as a team and follow what ran.”

That way, whoever runs the operation sees the machines and the history without opening Curator on each computer. To invite people and give them roles, see Team and workspaces.

Summary

1. “Execuções” is the history: “Lista de Execuções” shows what ran; “Fila de Execução”, what is waiting its turn.
2. Each row gives the date, project, origin (“Manual” or “Gatilho”), status, tokens, machine and report.
3. Filter with “Projeto:”, search with “Buscar:” and use “Exportar” to keep the history.
4. Triggers make the automation start on its own on this computer: at a set time or on the new items in a queue.
5. Before the trigger: run it once, test the parts and turn on the Curador, which fixes technical errors without waiting for you.
6. In the web portal you follow machines, triggers, runs, queues and team, and send runs to a machine.