scheduled-events-and-queues skillA
scheduled-events-and-queues is agent-read markdown (skill) from mendixlabs/mxcli: Scheduled events (Mendix's cron) and task queues in MDL — the eight repeat variants and the fields each takes, and what a queue does and does not throttle. Use when running a microflow on a schedule, or bounding how many background tasks run at once..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Scheduled Events and Task Queues
## When to Use This Skill
Use this skill when the user wants to:
- Run a microflow on a schedule ("every night at 4", "hourly", "cron", "batch job")
- Inspect or change an existing scheduled event
- Limit how many background tasks run at once (a task queue)
- Run a microflow or Java action call on a queue (`IN QUEUE`)
**These two features are unrelated.** A scheduled event does **not** go through a
task queue. Its own concurrency control is `OnOverlap`.
## Scheduled Events
Mendix's cron: run a microflow on a repeating schedule.
```sql
-- Inspect
list scheduled events;
list scheduled events in Ops;
describe scheduled event Ops.NightlyCleanup; -- re-executable MDL
-- Create
create scheduled event Ops.NightlyCleanup (
Microflow: Ops.SE_Cleanup,
Repeat: Daily,
HourOfDay: 4,
MinuteOfHour: 0,
TimeZone: Server,
Enabled: true
);
drop scheduled event Ops.NightlyCleanup;
```
`Microflow` and `Repeat` are **always required**. `show` is a synonym for `list`.
### Pick the Repeat first, then use only its fields
Mendix stores the repeat rule as one of eight types, and they differ in **which
…Read the whole file at its exact version.
How to install
mdr add mendixlabs/mxcli/scheduled-events-and-queues@git:20260923.53ff13cmdr add mendixlabs/mxcli/scheduled-events-and-queues@sha256:24ff3fc48bbf0467Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_peio76ybqyymltxp)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260923.53ff13c latest | 2026-09-23 | 53ff13c | 13,171 B | A | view · diff |
| git:20260922.4954f84 | 2026-09-22 | 4954f84 | 12,521 B | A | view · diff |
| git:20260821.ff81a24 | 2026-08-21 | ff81a24 | 10,687 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (13171 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
mendixlabs/mxcli · 124 stars · license Apache-2.0 · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_peio76ybqyymltxp GET https://markdownregistry.com/api/v1/resolve?ref=mendixlabs/mxcli/scheduled-events-and-queues GET https://markdownregistry.com/api/v1/blob/24ff3fc48bbf0467b00d6118b0b747fb19157685a60e7309e5faea7f60a52335
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.