Learn / Development guide

Find the cause before repeating an action.

Preserve the source, inspect current state, and report the smallest useful reproduction.

Development guide · source-reviewed foundation · public-package walkthrough pending

Keep recoverable work first.

If the app responds, Save As a separate copy and verify reopening. Do not delete preferences, media or caches as a first response. A project can depend on external sources and fonts. Automatic crash recovery is not promised.

For an unresponsive operation, record what was happening and inspect active render/proxy status before starting more work.

Start with the symptom.

SymptomFirst checks
Save failsRead the error; verify a writable folder; preserve the original and try a new path
Missing mediaLocate original sources; a proxy is not a substitute; preserve a copy before relinking
Missing font or changed wrappingRefresh/check actual face/style, bounds and destination availability
Controls fadedCheck selection, nesting, applicability, locks and lower promotion links
One edit changes several usesCheck whether you entered the shared source rather than an instance
Instance stops followingRevert its override; a matching typed value remains overridden
Unexpected motionInspect clip range, comp time, animation lanes and intermediate keys
Output is blockedRead pending template/slot/media or format-specific refusal
Wrong duration/transparencyInspect actual frame count/rate/alpha and destination interpretation
AI connected but no projectOpen editor/project normally and start with a state read

Saved output and uncertain sends.

For a known failed send, follow the candidate’s retry rules for unchanged verified output. If the outcome is unknown, inspect Resolve before repeating; the write may already exist. Files remaining after restart do not establish that old session-only retry state can resume.

Local render resume uses its original snapshot and job. Later source edits do not retroactively alter that render. Do not confuse render resume with sending another destination clip.

Make the problem reproducible.

  • App stage/version and OS; relevant GPU/driver context.
  • Resolve edition/version/route or AI client/version where involved.
  • Minimal steps, expected result, actual result and exact error.
  • A redacted capture and optional non-confidential sample.
  • Whether source/save/reopen and destination inspection succeeded.

Do not publish credentials, complete client configuration, customer media or personal paths. Avoid repeating uncertain external writes just to create a report.