Prepare a support request with useful screenshots and timings

A useful support request lets another person understand the problem without needing access to the entire production machine.

A practical procedure

1. Summarise the expected result, actual result and shortest steps that reproduce the issue.

2. Include the application version, affected time window and a tightly cropped screenshot of the relevant state.

3. Remove secrets and unrelated viewer information, then attach a small reproducible sample if appropriate.

Worked example: a fictional session

A fictional request includes a ten-second silent export and the selected-track screenshot, allowing support to inspect the routing question directly.

Check the limits

Large unfiltered log dumps can hide the useful evidence and expose unnecessary information.