Troubleshooting

“My automation does not fire”

1. Is it active? In the Automations list, it must show Active, not Paused. For a pack, the switch must be on Active, and the schedule must not say Paused until….
2. Does it target the right server? Look at Servers: … in the top bar (or Servers in the pack's settings). “1 server(s)” does not cover the others.
3. Is it suspended? A Suspended badge means the last person who saved it no longer has the required rights. Save it with an account that has them.
4. Do you have the permissions? See below: the permission to manage automations, plus the one for each action.
5. Did the trigger happen? Open the Log. “No runs yet.” means the trigger never happened on a covered server. Make it happen (a test player, or the simulator) and refresh.
6. Is a condition stopping everything? Run a Dry run with the values of the case, or Show on the canvas a run from the log: the If card that leaves through the wrong output is obvious right away.
7. A rate limit? The Limited (already done recently) result means a Rate limit step deliberately blocked what follows.
8. Did the player leave? A Skipped run can come from a player who left during a Wait step.

My conditions do not work as expected

• Missing data makes the condition false, except with the operator is missing. This is the case for Steam data not yet read: it sometimes arrives a few seconds after a new player joins. The Risky Steam account template therefore waits for Steam to answer before testing.
• A number is compared with a number: a text piece of data does not offer the operators more than or at least.
• To test a name, text comparisons ignore case. Regular expressions are written out in full, with no inserted data.
• If a card shows a red dot or if To fix before saving appears, saving is blocked until it is fixed.

The permissions needed

An automation acts on behalf of the organization. To save it, you need the Manage automations permission on the targeted servers (on the organization for a pack), plus the one for each action, on every targeted server.

If someone's role changes or they leave the organization, their automations become Suspended until someone with the rights saves them again. A file import also checks these permissions and tells you which one is missing.

The limits to know

Events emitted by an automation do not chain beyond 3 levels: past that, the chain stops.

Frequently asked questions

I can't edit an automation created by a pack.

That is normal: it is managed by the pack. Change its settings from Packs › Settings. If you want to edit it freely, click Detach in its editor: the pack will no longer update it.

I uninstalled a pack and my automations disappeared.

Uninstall deletes the automations the pack manages. To keep them, turn the pack off with the Active switch instead of uninstalling it.

The message arrived twice, or never.

Twice: an unstable connection restarts the trigger, add a per-player Rate limit. Never: look at the Log, the matching row tells you whether the run is Skipped (player left), limited or Failed.

Where can I see what my memory holds?

In the editor's Memory panel, or with the Memory button on the Automations page.

Something is still missing.

Write to support from the site's Support page: describe what you wanted to get, and what you see in the log.