We believe in keeping you in the loop with all the latest happenings in our courses and system. On this page, you'll find a comprehensive log of all the exciting changes, improvements, and additions we make to our courses and system. Whether it's a new feature, a course enhancement, or a system update, we've got you covered. Bookmark this page and check back regularly. We're committed to ensuring that your learning experience remains exceptional and that you have all the information you need to succeed.





AI edits previously had no recovery path, so a small change meant rebuilding by hand. To improve your efficiency, the workflow AI builder now tracks every iteration it creates. Each AI build or edit produces an artifact card in the chat, and any of them can be restored in a single click. Let’s learn what has changed!
⭐️How Do These Changes Affect You?
AI Version Indicator: Every build or edit from the AI Assistant produces an inline card in the chat, and the card matching the canvas carries a purple border, so the active iteration is always identifiable.

Synced with Version History: Clicking "Show in version history" opens the Version History tab, where AI and manual versions appear on a single unified timeline. Version History remains the single source of truth for version numbering.

Bidirectional Non-destructive Changes: Restoring an older iteration keeps newer ones restorable. Iterations can be moved between freely, and none are destroyed.

⭐️How To Use AI Iteration Versions?
Let’s learn how to access and restore AI Iteration Versions!
Prompt the AI Assistant to build or edit your workflow.

An artifact card appears in chat, with a purple border indicating it is the current version.

Prompt another change. The new card takes the border, and the previous card gains "Restore this version" in its three-dot menu.

Use the three-dot menu on any card to restore that iteration or open it in Version History.

Tying every AI iteration to a restorable artifact makes the assistant safe to boldly edit without risking lost work. Routing those iterations into the same timeline as manual versions keeps Version History authoritative and easy to use. We hope you enjoy it!