No-Code Workspace — Block Reference

AdvancedBlock usage recipe

Sleep Until (SLEEP_UNTIL)

Waits until a target time is reached

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

With Use absolute time (epoch ms) on, it waits until Target epoch ms; with it off, it waits for Wait from now (ms). For flows aligned to real clock time.

When to Use?

Use it to start work at a specific time or wait until a target computed with DATE_TIME.

How to Use?

Turn on absolute time and enter or bind Target epoch ms

Choose the check interval (default 100 ms)

Parameters

Target epoch ms

End moment (ms) with absolute time on; can be bound with the lightbulb

Wait from now (ms)

Relative wait when absolute time is off

Check Interval

Ms between checks (default 100)

Parameter	Description
Target epoch ms	End moment (ms) with absolute time on; can be bound with the lightbulb
Wait from now (ms)	Relative wait when absolute time is off
Check Interval	Ms between checks (default 100)

Example Usage

Compute the target with DATE_TIME (targetMs) → SLEEP_UNTIL with Target epoch ms bound to targetMs → run the report group

Combinations / Used With

COMBINATIONS:

DATE_TIME + SLEEP_UNTIL: Start by the calendar

TIME_SPAN + SLEEP_UNTIL: Relative target

Tip

For macros that run at the same time every day, the macro's daily or interval trigger is more reliable.

Warnings / Cautions

WARNING:

With a past target the block continues immediately

A very short check interval wastes battery

Step-by-Step Mastery: Basic → Advanced → Pro

The same block at three levels: a quick start, the real options, and professional techniques.

Basic

SLEEP_UNTIL waits until a real target moment, not a fixed duration. You give a Target Time timestamp or set a relative delay; once reached, the flow continues normally. Unlike a fixed-millisecond wait, it aligns to real clock time.

Advanced

There are two uses: with Use absolute time (epoch ms) on, it waits until Target epoch ms; with it off, it waits for Wait from now (ms). The check interval (default 100 ms, 1-60000 ms when bound to a variable) sets how often it checks whether the target is reached. It is ideal for waiting until a DATE_TIME-computed target (e.g. 09:00) and then running a group. If a past target is given the block continues immediately, so the target must always be in the future.

Pro

The foundation of calendar-based automation is feeding a DATE_TIME-computed target into SLEEP_UNTIL: get now with now_ms, compute the target hour's epoch ms, and if it is in the past add a day before SLEEP_UNTIL. Scale the Check Interval to the duration — for multi-hour waits 100 ms causes needless wakeups and battery drain; a few-second interval is enough for long waits. If multiple devices/macros trigger at once, add a small RANDOM_NUMBER jitter to the target to spread load (avoids a thundering herd). For macros that must run at the same time every day, use the macro's daily or interval trigger instead of one very long SLEEP_UNTIL; on Android 12 and later it needs Alarms & reminders access to fire on time.

Real-World Scenarios — Step-by-Step Recipes

Small, reproducible examples that combine several blocks — build them straight into your own macro.

Start the reporting flow at 09:00

1DATE_TIME → get now with now_ms and compute the 09:00 target (targetMs)
2SLEEP_UNTIL → absolute time on, Target epoch ms bound to targetMs with the lightbulb
3Once reached, run the HTTP_REQUEST and FILE_WRITE group

Add a random jitter to a relative target

1TIME_SPAN → 5 minutes, ms output: baseMs
2RANDOM_NUMBER → min=0, max=20000, Result: jitter
3SET_VARIABLE → targetMs = DateTime.nowMs() + baseMs + jitter
4SLEEP_UNTIL → absolute time on, Target epoch ms bound to targetMs with the lightbulb

Which Blocks to Pair With — Pro Combinations

This block is useful on its own — but it shines when paired with the right partners.

+ DATE_TIME

DATE_TIME computes the target time and SLEEP_UNTIL waits to it; the core of calendar-based triggering.

+ TIME_SPAN

Provides a readable duration unit for relative target calculations.

+ GROUP_CALL

Used to kick off the scheduled scenario once the target is reached.

+ RANDOM_NUMBER

Adds a random jitter to the target to spread simultaneously triggered macros.

Common Mistakes and Fixes

Giving a past target and being surprised the wait is skipped. Fix: verify the target is in the future, add a day if needed.

Using a very short Check Interval on a multi-hour wait and burning battery/CPU. Fix: raise the interval to the seconds range for long waits.

Passing locally formatted text as the absolute target. Fix: Target epoch ms must be a millisecond timestamp; get the time with DATE_TIME Now (ms) and compute from it.

Pro Tips

Splitting long waits into small steps instead of one SLEEP_UNTIL keeps the macro stoppable and responsive.

Do all math on epoch ms; always give SLEEP_UNTIL an ms target, never local text.

This Block's Code (Editor View)

Lua

The Lua below is what the Code Editor generates for this block with sample settings. Adding cases, branches, actions or loops, or changing settings, extends the generated code accordingly. Study it to see what the block does under the hood, to learn Lua, or to copy and adapt it. Use the Copy button (top-right) to paste it into the Code Editor, or “Try in Editor →” to run it in the live editor.

lua

Try in Editor →

local _deadline1 = DateTime.nowMs() + 100
while DateTime.nowMs() < _deadline1 do
 wait(10)
end

Note: generated code can evolve across versions; helper names (e.g. _reg1, m1) and internal optimizations may change. The logic and the called APIs reflect the block’s behavior.

Block ↔ Lua Mapping →

Shared Controls for This Block Family

The guidance below is not identical for every block. It summarizes the professional controls that most often repeat in the selected block family.

🛡Protection Layer

Blocks like ERROR_HANDLER and SLEEP_UNTIL strengthen a flow; they should not be used to hide unclear core logic.

📉Infinite Wait Risk

Always define an exit scenario and observable bound when using sleep-style waiting conditions.

🧭Central Error Policy

Global error handling should belong to one policy. Avoid multiple competing error strategies in the same project.

Builder vs Lua Boundary

Raw touch pointer lifecycle stays code-first

TOUCH and TOUCH_BREAK cover recipe-style touch flows. Raw pointer choreography such as Touch.down, Touch.move, Touch.up, Touch.dispatch, Touch.reset, Touch.breakAll, and Touch.releaseAfter is not exposed as a first-class builder block.

Touch.downTouch.moveTouch.upTouch.dispatchTouch.resetTouch.breakAllTouch.releaseAfter

Bounded dialog design is builder-backed; freer composition stays code-first

The DIALOG block and dialog designer cover a bounded field set in the builder: Info Text, Text Input, Checkbox, Description, Radio Group, Dropdown, Multi Select, Tab Group, Date Time, Number Range, Slider, Image Picker, Color Picker, File Picker, Recorder Picker, Tag, Signature, and Spacer. The buttons are designed too: the Positive button and Negative button tabs set each button’s text, background, and border color, corner radius, and minimum height next to a preview. Freer Setting.builder composition, multi-step wizard flows, and mixed HUD/dialog choreography still do not map 1:1 into the builder.

Coming soonv1.0.51Two more fields: Agent Detect references (agent_detect_editor) lets the user pick a saved reference set or add and edit references, and Save confirms the selection; Navigation setup editor (navigation_editor) edits a saved map, marker and route from the Dialog and returns the setup and route selection without moving the character.

Setting.builderDialogHudTextViewAgentDetectEditorNavigationEditor

Advanced HTTP request chaining stays code-first

HTTP_GET, HTTP_POST, and HTTP_PUT cover common fixed-method flows; HTTP_REQUEST covers one bounded request with method, header lines, body, content type, query parameters (GET and DELETE), timeout, and a bounded retry. These blocks never throw; they write the status code (-1 on a network failure). Cookie handling, chained request objects, and lower-level client flows still need the code editor.

Request()Request.setCookieRequest.getCookiesCUSTOM_CODE

General programming surfaces stay code-first

The MAP, LIST, JSON_PARSE, REGEX_MATCH, and METRICS blocks cover the everyday cases: map actions, a static list, reading a value from a JSON path, regex match, find, replace, and split, and metrics actions. The rest of the Map, Array, JSON, Regex, and Metrics APIs (for example Array sort, filter, and map) is broader than the builder recipe model and stays on the CUSTOM_CODE and code editor side.

MapArrayJSONRegexMetrics

Low-level runtime and Lua composition stays code-first

Runtime helpers, raw Request objects, Lua built-ins such as print/pcall/xpcall, and free-form object chaining patterns are represented through CUSTOM_CODE or the code editor.

RuntimeRequestprintpcallxpcallCUSTOM_CODE

Debug Mode and Breakpoints

Each block card now exposes an independent breakpoint toggle. When enabled, the breakpoint preference is stored with the block.

Breakpoints are only emitted into runtime code when Debug Mode is enabled from Visual Builder settings. When Debug Mode is off, breakpoints stay saved but do not pause execution.

Use ASSERT for fail-fast validation, and use breakpoints for step-by-step tracing and controlled pauses in the same flow.

Variable Scope

Variables defined with SET_VARIABLE are accessible throughout the macro (global scope). All blocks can read/write the same variable.

However, a variable defined inside a GROUP will be 'nil' (undefined) until the GROUP executes. Blocks outside the GROUP using this variable may produce unexpected results.

FOR_EACH loop variables (item and index) only carry valid values inside the loop body. Outside the loop they are outside local scope and should not be used.

TRY_CATCH error variable is only valid within the catch block. If the try block succeeds, the catch branch is not entered and the error variable remains undefined.

TIP: Before using a variable inside a GROUP, assign a default value with SET_VARIABLE outside the GROUP. This way the variable won't be nil even if the GROUP has not run.

Inline Expressions

You can embed variable values and calculations into text fields using {{ expression }} syntax. Expressions inside double curly braces are evaluated as Lua code and the result is inserted into the text.

Syntax

{{ expression }}

Examples

Skor: {{ score + 1 }} → "Skor: " .. tostring(score + 1)

{{ name }} kazandı! → tostring(name) .. " kazandı!"

X:{{ x }} Y:{{ y }} → "X:" .. tostring(x) .. " Y:" .. tostring(y)

Supported Blocks

SET_VARIABLELOGCOMPARECLIPBOARD_WRITENOTIFY_TOASTKV_SET

Security Note

Expressions are checked by the sandbox policy. Security-sensitive calls like loadstring, require, debug are automatically blocked.

General Tips

Keep scan regions as small as possible — improves speed, reduces false matches.

Always add an exit condition when using infinite loops (BREAK, timeout, or conditional exit).

Use network operations and error-prone steps inside TRY_CATCH.

If you need global error handling, use the Error Handler (ERROR_HANDLER) block as a singleton in the project.

Small coordinate offsets (CLICK/SWIPE) improve tap accuracy across different DPI and screen scales.

Customize macros with Dialog block — different parameters each run.

Define repeating steps once with GROUP_CALL, call from many places.

Cross-macro local library

Local Shared Macro Area

The Local Shared Macro Area moves blocks, variables, dialog fields, gallery assets, and imported media dependencies between macros on the same device. It is device-local, not cloud sync, not Firebase sharing, and not a replacement for public macro sharing.

Professional usage model: put a reusable login flow, common scan region, shared dialog form, variable group, template image, color profile, replay recording, or imported PLAY_SOUND media file into the shared area from one macro, then import it from the relevant + menu in another macro.

VISUAL_BLOCKSVARIABLESDIALOG_FIELDSTEMPLATE_IMAGECOLOR_SWATCHREPLAY_RECORDMEDIA_FILE

Send to the shared area

When one item or a multi-selection is active, the shared-area button can copy the selected part from the workspace, group, true/false action branch, dialog, and variables surfaces into the device-local library.

Import into another macro

The shared-area entry under the + menu imports the selected item into the surface that opened it. Main workspace, group, action branch, dialog, and variables each receive the compatible item type.

Share gallery assets

Gallery items include template images, color swatches, replay records, and imported audio/media files. They can move between macros on the same device so repeated templates, colors, recordings, and PLAY_SOUND media assets do not need to be captured again.

Keep it clean

The shared area is not a permanent dumping ground. Delete stale shared items from the shared-library panel; imports create a copy in the target macro and do not rewrite the source macro flow.

Checkpoint: after importing, review block names, linked template/image/color/record/media assets, and variable names in the target macro. The shared area creates a copy; delete stale shared items from the shared-library panel to keep the library clean.

AI assistant

Build a block chain with MH AI in natural language

Tell MH AI what you want in plain language; it proposes the right block sequence and lands it in the workspace after you approve. In the current release it works with cloud providers such as Gemini, Claude, and OpenAI; on-device local models are on the roadmap.

Learn more →