Answers to the questions that come up most often when installing, running, scheduling, and securing PyAutoFlow.
It's a Windows desktop app for writing, running, and scheduling Python code. Everything a beginner needs — editor, run output, scheduling, run history, and learning courses — is in one window, so you can run your first script right after installing.
You don't have to set up a development environment yourself, and scripts run in an isolated environment so a mistake in your code is unlikely to affect the rest of your PC.
Yes. If the Python environment chip at the bottom-left of the sidebar shows Not connected, click it. Settings → Python environment opens, and one click on [Install Python] downloads and configures a Python runtime for the app (internet required, one time only).
Any other Python already on your PC is left untouched. When it finishes, the chip changes to Connected and shows the version.
Store Python runs inside an app container, which isn't compatible with PyAutoFlow's isolated execution, so it is deliberately excluded from the list of interpreters. Sometimes what looks like python.exe is only a stub that opens the Store page.
Use the [Install Python] button above, or install from the standard installer at python.org.
엣지비트 as the publisher — a blank or different publisher means the file is not official.More info, check that the publisher is 엣지비트, then choose Run anyway. First make sure you downloaded the file from the official download page.The actual .py files live under Documents\PyAutoFlow\Scripts. The file name is what you see in schedules and run history, so a name that says what the script does makes it much easier to find later.
Uninstalling the app leaves this folder in place.
Press Run at the top right of the editor and the tabs below show the result.
Past runs are in Run history in the left menu. It records the time of failure and which Python environment was used, which helps when you're checking whether the same error keeps repeating.
Read a traceback from the bottom up.
NameError: name 'prnt' is not defined means you called a name that doesn't exist — usually a typo.File "...", line 12 is the line in your code where it happened. If several files are listed, look at the last one with your own file name.ModuleNotFoundError (library not installed), IndentationError (indentation), TypeError (wrong type), FileNotFoundError (file path).If you're still stuck, don't stay stuck alone. Post in Q&A with (1) what you were trying to do, (2) the full error message, and (3) the code that fails. The ask form has a separate box for pasting code.
Use the Packages tab below the editor to install, upgrade, or remove libraries. Most ModuleNotFoundError problems are solved right there.
If you run several scripts, a virtual environment is safer: each project keeps its own library versions, so updating one script's dependencies won't break another. Create and select one in Settings → Python environment.
Check the encoding of both the file and the output.
open('data.csv', encoding='utf-8')encoding='cp949' for Korean) is sometimes the right one.Yes. The Debug tab below the editor lets you set breakpoints, step through your code, and inspect variables.
Note that debugging is disabled at the strictest security setting. The debugger needs a channel between the app and the Python process, and strict mode blocks it. If you need to debug, lower the protection one step in Settings → Security & sandbox.
No. Scheduled runs happen while PyAutoFlow is running. If the PC is powered off, asleep or hibernating, or the app is fully closed, the run is skipped.
For a job that really has to run at a set time, make sure the PC is awake and the app is open during that window.
Check these in order.
For frequency you can pick once, hourly, daily, or weekly, or enter a Cron expression directly if you're comfortable with it.
It runs your script in an isolated environment, which greatly limits what it can do to files outside the working folder or to the system. The companion script safety check analyses code without running it and points out potentially risky calls such as shell, network, or dynamic execution.
We recommend leaving it on, especially the first time you run code from the internet, from the community, or generated by an AI assistant. You'll find it in Settings → Security & sandbox.
Under protected execution, a script starting another program (a child process) is blocked by default. That's what WinError 367 ("The operation could not be completed") means when subprocess.run(...) or an external command fails.
If that's intentional, allow shell / external program execution in Settings → Security & sandbox. Keep in mind this widens what a script can do on your PC, so only change it after you've read the code.
Also note that isolated runs have no console attached. Reading input with input() works normally, but code that requires a real console — reading the terminal size, for instance — can fail.
Under protected execution, writing is allowed only inside the working folder. Paths outside it are always blocked, regardless of settings, and if you turn write permission off, even the working folder becomes read-only.
open('result.csv', 'w') instead of an absolute path like your Desktop or C:\.Protected execution can restrict a script's network access. If your connection is fine but only the script fails, check that setting first — it's the network item under Settings → Security & sandbox.
A corporate proxy or firewall, or your antivirus's network protection, can also block the Python process.
Protected execution caps how much memory a script may use and stops runs that take too long. Reading a huge CSV in one go, or growing a list forever, hits this often.
You can see the current limit in Settings → Security & sandbox. If it's already at the maximum, you can't raise it further — change the code instead.
If the script is code you wrote yourself, you know exactly what it does (say, tidying files in a folder you chose, or calling an external program), and protected execution keeps blocking a permission you genuinely need — then yes, it's fine.
Leave it on when:
The app works without signing in, and in that case you're on Free.
After you sign up and verify your email, you get 30 days of Pro for free. No card required, and when it ends you simply return to Free — the app is never locked.
No. Cancelling only stops the next automatic renewal. You keep Pro until the period you already paid for ends.
You can cancel any time on the Pro page or in the app under Settings → Subscription.
Because this is digital content, withdrawal is limited once access begins — but under our own policy we offer a full refund within 7 days for monthly plans and 14 days for annual plans after payment.
Use the Request refund button on the Pro page. The request goes to our team and is processed after review (pressing the button does not refund you instantly). After that window, cancel instead: the next renewal stops and you keep using the time you've already paid for.
When a new version is available the app tells you. Follow the prompt and it updates, and your scripts, settings, and run history are kept.
It's best to update after you've finished what you're doing: save the script you're editing and check whether a schedule is about to fire. After updating, confirm that your Python environment is still connected.
No. Removing PyAutoFlow from Windows Settings → Apps → Installed apps leaves the scripts in Documents\PyAutoFlow\Scripts, along with your settings and run history, in your user folder. Reinstall and you pick up where you left off.
If you want everything gone, delete that folder yourself after uninstalling.
한국어 · English · 日本語 · Монгол · Tiếng Việt · 繁體中文