TinyTask Pro Macro Won’t Load: How to Fix It

A saved workflow can fail because the file is empty, incomplete, edited into invalid JSON, stored in a protected location or created by a version with different expectations. Recovery begins by preserving the file exactly as it is.

Work on copies and use harmless test data. If the macro contains confidential text, do not upload it to a public validator.

Protect the original file

Close TinyTask Pro and copy the failed macro to two locations. Rename one copy with -recovery-copy while keeping the extension unchanged. Record the file size, modified date and TinyTask Pro version that created it.

If the size is zero bytes, the recording data was not saved into that file. Recovery will depend on a backup, previous version or unsaved application state rather than JSON repair.

Prove that loading works

1. Open the same TinyTask Pro release.
2. Record two harmless actions.
3. Save the new macro to Documents.
4. Close and reopen TinyTask Pro.
5. Load the new file.

If the new macro also fails, check application permissions, storage access and the installation before modifying the old file. If the new one loads, the problem is specific to the original macro or its location.

Check extension, path and permissions

Confirm that Windows has not hidden a double extension such as workflow.json.txt. Move a recovery copy to a short local path in Documents; avoid email attachments, cloud placeholders, read-only media and network shares during diagnosis.

Make sure the file finished syncing or downloading. A cloud icon can indicate that only a placeholder exists locally.

Inspect JSON without exposing data

Open the recovery copy in a plain-text editor. A JSON file should have balanced braces or brackets, quoted field names and no obvious truncation halfway through a value. Do not “fix” unfamiliar fields based on guesswork.

If you manually edited the file before it failed, undo those changes from a backup. A private offline JSON parser can identify the line of a syntax error, but a syntactically valid file can still contain data TinyTask Pro does not support.

Test version compatibility

Try the macro first in the version that created it. Then test a copy in the current release. Read the release notes for file-format or playback changes.

Do not repeatedly save an old macro from multiple versions. Keep a pristine original and clearly labeled converted copies until the workflow is verified.

Recover what can be recovered

Search versioned backups, cloud file history and Windows backup locations for an earlier non-zero copy. If the file opens but stops at one point, split or re-record only the failed portion.

When contacting tinytask.org/blog/ support, provide the product version, file size, error text and whether a fresh macro loads. Share a redacted file only through a channel you trust.

Prevent future macro loss

• Use versioned names instead of overwriting.
• Keep one local and one backed-up copy.
• Close recording cleanly before shutting down Windows.
• Test loading immediately after saving.
• Back up before application updates or manual edits.
• Store secrets outside macros where possible.

Frequently asked questions

Can TinyTask Pro repair a zero-byte macro?

A zero-byte file contains no saved workflow data. Restore a backup or re-record the workflow.

Can I paste my macro into an online JSON checker?

Avoid public tools if the macro may contain confidential data, credentials or customer information. Use an offline method or a redacted copy.

Why does a macro open in one version but not another?

The saved format or validation rules may differ. Test the creating version and consult release notes before conversion.