Use TWS’s supported log-export process to obtain readable diagnostics. Keep the event time and the client ID with the case. A file copied from the log directory may be encrypted and may not be the log support needs.
Educational software guidance. Trading involves risk. Read the financial and information disclaimers.
Step by step
- 1 Identify the date, time zone, client, and action that failed.
- 2 Check that the needed logging was enabled during that event.
- 3 Open Help → Troubleshooting → Diagnostics → API Logs. In the View Logs dialog, select the log day you need. If the list is empty, check whether logging was enabled before the event.
- 4 Use Export Today Logs for today, or Export Logs for selected days. These controls may be disabled when there is no log to export. Inspect the saved file before sharing it.
- 5 Send the needed file through the support channel, with a short description and credentials removed.
A practical example
A file ending in log may still be encrypted. If support needs readable API messages, follow the TWS export steps linked below. Tell them the date and the client ID used by the app. Also tell them what action to find. A short note such as one request failed just after reconnect is more useful than a file sent with no explanation.
Screen reference



Mistake to avoid
Common questions
Which is better: a screenshot or a log?
A screenshot shows the symptom; a needed log often shows the sequence that caused it.
Should I upload every log file?
Start with the requested files and period rather than other account history.