Skip to content

Output Trigger Setup Changes Intermittently Not Applying (7.7.17)

Summary

On Flair 7.7.17, changes made in the Output Trigger Setup dialog intermittently fail to take effect — sometimes the new trigger configuration works, sometimes it silently doesn't, with no error shown. The only fully reliable workaround at close/reopen level is closing and reopening the job file. A lighter workaround, confirmed by another operator who'd hit the same bug: enable Classic in System Configuration, make the trigger changes in Classic running in the background, switch back to Flair 7, and click "Flair engine update."

Symptoms

  • Output Trigger Setup dialog changes are made and applied (Apply clicked).
  • The new trigger behavior sometimes works, sometimes doesn't — inconsistent, not tied to a specific setting.
  • No error message or warning is shown when the change fails to take effect.
  • Closing and reopening the file makes the trigger changes start working correctly again.
  • Reported specifically on Flair 7.7.17, running Flair 7 only (no Classic running in the background).

Community Guidance

[RESOLVED — WORKAROUND] Edit in Classic, Then Trigger a Flair Engine Update

Community — Stafford — 14 July 2026

"Try going to Flair Classic in the background changing the triggers settings then back to Flair 7 and click Flair engine update... If that works then it's the same bug we had, not totally sure we reported it though."

Steps:

  1. In System Configuration, enable Classic to run alongside Flair 7.
  2. Make the Output Trigger Setup changes in Classic, not in Flair 7 directly.
  3. Switch back to Flair 7 and click Flair engine update.
  4. Verify the trigger change has taken effect before relying on it in a take.

If this workaround isn't practical (e.g. Classic isn't licensed/available on that machine), the fallback is simply closing and reopening the job file after making Output Trigger Setup changes, and re-verifying the trigger fires correctly before shooting.

confidence_score: 0.68