Creating and running tasks

A task in Lusiesta Studio is one specific action on one specific phone: upload a video, warm up a feed, apply a proxy, install an app. Everything the program does with your devices goes through the task dispatcher, which makes the Tasks page the single control point for the whole farm. Below you will find where tasks come from, what happens after you start one, how to read the statuses and what to do when a task fails.

One task = one device

The app never creates a single shared task for the entire farm. If you select ten phones and hit start, you get ten separate tasks, one per device. Each has its own status, its own result and its own ID in the form T-0001. This is deliberate: a phone that fails is visible by name, while the rest keep working.

For publishing the rule is carried all the way through: one task - one device - one video. Each device pulls its own file from the shared clip queue, so ten phones take ten different videos, and the next run picks up the next ones. The engine never loads a batch of clips onto a single phone.

Types of tasks

The catalog of task types is fixed:

• Video publishing (Publishing category) - uploading a clip to TikTok, Instagram or YouTube. In the task list it appears as "Video upload".
• Warmup (Activity category) - scrolling the feed with randomized actions. Listed as "Instagram warmup", "TikTok warmup" or "YouTube warmup".
• Proxy setup (Network category) - running the scenario that applies a proxy on the phone.
• Clone installation (Preparation category) - rolling app clones out to devices.

Three more types exist in the catalog but never appear as rows in the task list: APK installation, Upload to gallery and Clear gallery run straight from the "Quick actions" buttons, with no queue. Two more operations live outside the dispatcher as well: checking proxies with the "Check all" button on the Proxies page, and installing the input agent with the "Initialize agent" button in the right-hand panel. All of them run on the spot and leave no row in Tasks.

Where tasks are created

There is no "create task" button on the Tasks page: tasks are created by the working pages, and Tasks simply shows the outcome.

• New publication - the button in the ACTIONS section of the sidebar, launched with Start publishing.
• The Warmup tab on the Instagram, TikTok and YouTube pages - the Launch block and the Start button.
• The Proxies page - applying a proxy to a device creates a Proxy setup task.
• The Clones page, Installation step - the Start installation button creates Clone installation tasks.

The buttons in the Quick actions block of the right panel (Install APK, Upload to gallery, Clear gallery) act on the selected devices directly: progress is visible on the Logs page, and they add no rows to the task list.

How to select devices

1. Connect the phones over USB and make sure they appear on the Home page. The device list refreshes automatically every few seconds.
2. Open the page you need and find the Devices panel. It has a "Selected X / Y" counter plus the All and None buttons.
3. Tick the phones and start the task. Your selection is remembered, so you do not have to tick them again the next time you open the page.

Device numbers ("#1", "#2" and so on) are consistent across the product: the same phone keeps its number in the grid, in publishing, in warmup and in the proxy list. Before tasks are created the list is filtered down to the phones that are actually connected, so a task never hangs on an offline device. If nothing is selected, you will see "Select at least one device." or "No devices selected".

What happens after you start

Between the button press and the first real action on the phone screen, a task passes several checks:

1. The server confirms access. Tasks will not start without a valid license, and that decision is made on the server side, not in the app.
2. Device limit of your plan. Phones above the limit do not run tasks: the task ends immediately with "Plan limit exceeded: devices allowed - N". Details in Plans and the device limit.
3. Input agent check. For warmup and publishing the app verifies that the Siesta agent is installed on the phone and has been granted accessibility access. If not, the task fails with a clear message telling you exactly what to tap. See The Siesta input agent.
4. Execution. The task switches to In progress, the work runs in a separate thread, progress is written to Logs, and the result appears in the task row once it finishes.

The Tasks page

The page is titled Tasks, with the subtitle "Manage and track task execution on your devices". Four counters sit at the top: Total tasks, Completed, In progress and Errors (the last one also covers tasks you stopped manually).

Below them is a table with the columns Status, Task type, Platforms, Device, Time, Result, Actions. The filters are All tasks, Active, Scheduled, Completed and Errors, next to a "Search tasks..." field. At the bottom you get pagination ("Showing X-Y of N tasks") and a "Per page:" selector with the values 6, 10, 15, 25 and 50. When nothing matches, the page shows "No tasks found".

Read the statuses like this: Scheduled means the task is waiting for its time, In progress means it is running right now, Completed means success, Error means a failure, Stopped means you interrupted it yourself. Times are written in plain language: "Today, 14:30", "Tomorrow, 09:00" or "12.08, 09:00", and running tasks show how long they have been going.

Stopping and deleting

Every row has three buttons in the Actions column: stop (available for active and scheduled tasks), a menu and delete. The menu contains Copy ID and Report an error.

Stopping is cooperative: the app raises a cancel flag and the handler checks it at the next safe step. That is why the phone does not stop instantly but only after the current action - the upside is that nothing is cut off in the middle of an operation. A task that has not reached execution yet is marked "Stopped by user" right away. Tasks that already finished (success, error, stopped) cannot be cancelled, only removed from the list.

Closing the app does not move tasks into the background. The execution thread does not survive a restart, so everything that was In progress or queued is marked with the error "Interrupted by an app restart" on the next launch. Plan long warmups so that you do not shut the computer down in the middle of the run.

If a task ends with an error

The task row shows a short reason: ADB not found, no files to upload, scenario not received from the server, plan limit reached, agent not installed. From there:

1. Check that the phone is online on the Home page and that its screen is unlocked.
2. Open Logs and filter by the device in question - you will see exactly which step it stalled on.
3. If the cause is unclear, click Report an error: a diagnostic archive with a screenshot, the screen tree and the log was already captured automatically at the moment of the failure and will be attached to your report. More in One-click error report.

Once you have fixed the cause, running the task again is perfectly safe: a new task is created from scratch on the same devices, and the old row stays in the history.