Flair Crashes Cancelling Speed Warnings — Move Lost From Current Job¶
Flair Crashes Ongoing All rigs FLAIR_CLASSIC
Summary¶
In Flair Classic (confirmed on version 7.2), speed warning dialogs sometimes appear for every axis on a move that has already been calculated successfully and run without issues. If the operator dismisses these warnings rapidly under time pressure, Flair can crash — and the move may be completely lost, not recoverable from "current job" after restart. Simply aborting and re-running the move without rushing through the warnings usually clears the condition.
Symptoms¶
- Speed warnings appear simultaneously for all axes on a move that is known-good and has run before
- Warnings appear during a forward run command before the move starts
- Rapidly clicking through warnings triggers a Flair crash
- After crash and restart, the move is absent from "current job" — data is lost
- Condition is intermittent — same moves run fine on subsequent attempts
- Confirmed on: Flair Classic 7.2 (multiple rigs), possibly 7.19
Root Cause¶
The exact root cause is not confirmed from community discussion. Possible contributing factors:
- Flair Classic recalculating speed limits at run time and generating spurious warnings when the calculation produces borderline values
- Rapid dialog dismissal (clicking OK multiple times quickly) creating a race condition or state corruption in Flair
- The crash may also cause the current job buffer to be cleared before Flair can write it back to disk
"This has happened to me several times in Classic, on different systems, and normally you just cancel all the warnings and hit Fwd Run again and it's fine." — Jeremy Andrews (2023-04-26)
Resolution¶
[CONFIRMED] — Abort and re-run without rushing¶
- When speed warnings appear, do not click through them rapidly.
- Cancel the run (Abort).
- Re-issue the Forward Run command.
- Warnings typically do not reappear on the second attempt.
- If they do, dismiss them one at a time, not in rapid succession.
"Abort move and rerun resolves the issue. I'm not quite sure what's happening with that." — Chavez.Camera (2023-04-26)
[CONFIRMED] — Save the move before each run on location¶
On busy shoots:
- Always save the current job to disk before running.
- If Flair crashes mid-dismissal, the saved file on disk will be recoverable even if "current job" is lost.
[ONGOING] — Report to MRMC¶
The speed warnings on pre-calculated moves are a known intermittent issue not yet fully resolved as of 2023-04-26. Submit a Flair Report (from within Flair) when it occurs to add to MRMC's case history.
Data loss risk on location shoots
If the crash occurs and the move was not saved to disk, it cannot be recovered. Save frequently during all location work.
Evidence from Community Chat¶
"In other news, has anyone been experiencing speed warnings appearing for every axis, when running a move in Classic that has already been calculated OK and running fine? This has happened to me several times in Classic, on different systems, and normally you just cancel all the warnings and hit Fwd Run again and it's fine. But yesterday I was about to shoot, got the screen full of speed warnings, and as I was cancelling them (in a hurry) Flair crashed, I got the Windows blue circle of confusion and my move was lost... not even in 'current job' when I rebooted." — Jeremy Andrews (2023-04-26)
"Yes, I've actually been running this issue today. Abort move and rerun resolves the issue." — Chavez.Camera (2023-04-26)
"Ok.. thanks. We're running 7.19 classic on our rigs with 7.2 on a test system.. just good to know what to look out for. Is not nice to get glitches like that when you're under pressure…" — Dig (2023-04-26)
WhatsApp Excerpts¶
- 2023-04-26 05:20 - Jeremy Andrews reported speed warnings appearing for every axis when running a Classic move that had already calculated and run correctly. He normally cancelled the warnings and ran again, but when he cancelled them quickly under shoot pressure Flair crashed, produced the Windows blue circle, and the move was missing from
current jobafter reboot. - 2023-04-26 05:27 - Chavez.Camera confirmed seeing the same issue that day and said aborting the move and re-running resolved it.
- 2023-04-26 05:34 - Dig asked which Classic version was involved.
- 2023-04-26 05:35 - Chavez.Camera reported running Flair Classic 7.2 from 1 March 2023.
- 2023-04-26 05:37 - Jeremy Andrews said he believed the occurrences were on Classic 7.2 across rigs in different locations, possibly including Milo.
- 2023-04-26 05:53 - Jeremy Andrews said this was the first time the warnings led to a crash; the move was lost, but he rebuilt it from playback overlay because it was a simple two-keyframe orbital.
Related Issues¶
- See also: Flair Crashes Opening Graph View — Axis Type Set to 'Unused — Flair crash from invalid axis type in Graph View
Revision History¶
| Date | Change | Editor |
|---|---|---|
| 2026-05-24 | Initial extraction | Tom D / Claude Code |