Known Bugs

This page lists known cases where InvokeAI does not yet behave as this documentation describes, or no longer behaves as v6 did. Each entry explains what happens instead and how to work around it. Entries are removed once the fix is released.

v7.0.0-alpha

Plain-HTTP access: another tab can take a still-open tab’s unsaved changes

Documented behavior: If a change cannot be saved yet, your browser keeps it and the tab that made it keeps retrying until the save goes through. See Saving and syncing.

Current behavior: When Invoke is opened over plain HTTP from a network address (for example http://192.168.1.20:9090, from another computer or from the one running Invoke), the browser turns off a feature Invoke uses to tell open tabs apart (Web Locks), so Invoke cannot tell whether another tab is still open. Opening Invoke in another tab, or reloading another tab, then takes over the unsaved changes a still-open tab is holding: an edit whose save had not finished when the tab was hidden, or one kept while the server was unreachable. The second tab saves them, and undoing the edit in the first tab no longer removes it.

Workaround: Open Invoke over HTTPS, or at localhost on the computer running it, where browsers provide Web Locks.

Plain-HTTP access: copying is off and some project actions work in one tab only

Documented behavior: Copy buttons put text and images on your clipboard. Deleting a project, resolving a save conflict, and discarding queue recovery data each wait until no other open tab is still running that project’s queue.

Current behavior: Over plain HTTP from a network address, the browser turns off clipboard access as well as Web Locks. The Launchpad shows a notice saying so, which you can dismiss for that address. Then:

• Copy buttons and copy menu items stay visible but disabled, and say that copying needs HTTPS or localhost.
• On the canvas, the copy, cut and paste shortcuts show a message that they need HTTPS or localhost.
• Deleting a project, and Discard or Save as new in a save conflict, work in the current tab only. Invoke still refuses while it knows of queue runs for the project, but it cannot see runs in another open tab that it has not recorded yet. Keep Invoke open in one tab while you do these.
• Discarding queue recovery data is refused, because Invoke cannot confirm that no other tab is still running those runs. You can still export it.

Workaround: Open Invoke over HTTPS, or at localhost on the computer running it, where browsers provide both.