Q100634: Using log files from Flix to start troubleshooting issues

Pete

Updated: February 03, 2026 00:21

Created: January 20, 2026 15:58

SUMMARY

This article explains how to troubleshoot Flix problems by using its log files.

MORE INFORMATION

Flix keeps 3 different log files - Flix server logs, Flix transfer util log and Flix client log. These log files help to understand what went wrong in Flix.
More information on what each log file includes and where it is located can be found in our Flix 6 Log Files Learn Page.

FLIX SERVER LOG

The Flix server log contains information about what the server is doing and where it is possibly failing. This log file will have information for:

publishes to Editorial
clips found during an XML or AAF import to Flix
QuickTime generation
user authentication

The log file can be quite large. To make it easier to find the information you need, you can look for the user’s username, the time the error occurred or just search for the word “error”. If you have multiple servers running, you should look at each server’s log file as Flix spreads all the tasks between the different servers.

trimOut Error

Here is an example log from a job (publish) by user username which ran on July 12th. It ran on the hostname server. It failed because there was a problem with the trimOut setting on an animated panel.

time="12 Jul 21 14:19 PDT" level=error msg="job failed, stopping chain" func="runtime.goexit:" Job="Publish image job" ThreadClientID=e728f608-00cf-413f-9190-3829bbe9e20c ThreadServer="Server{fa60a239-8090-4076-a44a-f4f97448edaa |hostname}" ThreadUser="User{username}" error="trimOut set to 55, only 40 media objects available on panel 3710"

If you find an error in the logs, you can check if it was already reported as a bug by searching the Flix Bug Tracker. Looking for the trimOut error above will take you to this bug - ID 442381 - [S] From/To Avid: Clip overlapping the beginning of one with an effect will cause incorrect trim in/out in Flix, preventing the publish back to Avid. It contains a workaround for the problem - to lower the trimOut setting for panel 3710 from 55 to 39. 39 is the number of available media objects (40) minus 1. You can change the trimOut setting in the property panel in Flix.

Context Canceled Error

A common error is the “context canceled” error. This is an error with something that broke earlier and the job couldn’t finish. You should look for errors earlier in the logs to understand what the problem is. In the below example, Flix was trying to publish, but it failed because the sequence revision was invalid.

ThreadClientID=af9e0cb8-bd3d-41d3-8307-5f56ce7b9eaf ThreadServer="Server {c64c33d7-d658-43b1-abf6-5798332738e7 | hostname}" ThreadUser="User{admin Admin user}" error="sequence revision is not valid" time="22 Dec 20 18:38 GMT" level=info msg="exiting after running job, chain failed" func="balancing.RunChainLocally:" ThreadClientID=af9e0cb8-bd3d-41d3-8307-5f56ce7b9eaf ThreadServer="Server {c64c33d7-d658-43b1-abf6-5798332738e7 | hostname}" ThreadUser="User{admin Admin user}" error="context canceled"

FLIX TRANSFER UTIL LOG

The Flix transfer util log contains information about file transfers between the server and the client. The speed of the transfer is dependent on a few things:

The internet speed of the Artist’s computer
How busy is the VPN server (if using a VPN connection).
How busy are the Flix servers.

The Flix file transfers are split into small chunks. If a small chunk fails to transfer, it will take less time to transfer it again. The transfer util log keeps track of each chunk being transferred. It looks like this:

time="2021-02-18T02:41:37+08:00" level=info msg="attempting to send chunk" Chunk="ClientChunk{/var/folders/lz/z0lt0xd159s_9kgvpnbsqkp00000gn/T/015350570/6o7ztCyrFZRnS218_211566_TA_1350_v02_074.psd/11_225992399 index#11}" time="2021-02-18T02:41:37+08:00" level=info msg="attempting to send chunk" Chunk="ClientChunk{/var/folders/lz/z0lt0xd159s_9kgvpnbsqkp00000gn/T/015350570/6o7ztCyrFZRnS218_211566_TA_1350_v02_074.psd/22_019408780 index#22}"

FLIX CLIENT LOG

The Flix client log contains information about actions that happen on the artists’ computers:

Flix client startup,
Communication between Flix and Photoshop,
SBP import information
File transfers between the Flix client and server.

Download Timed Out Error

In the below log example, the Flix client was able to download files from the server until 18:59:14.932 and then something happened (probably the VPN connection to the studio was disconnected) and the client failed to download more files. Check if the artist's computer had a working connection to the Flix server and if the server was accessible. If the VPN was disconnected, reconnect and try to download the panels again.

[2021-03-29 18:59:14.932] [debug] Media object transfer complete, 837623:544194172.png [2021-03-29 18:59:14.951] [error] media object (837662) download timed out [2021-03-29 18:59:14.951] [error] media object (837665) download timed out [2021-03-29 18:59:14.952] [error] media object (837655) download timed out

RECOGNISING A PHOTOSHOP ACTION

Opening panels from Flix into Photoshop and sending panels from Photoshop to Flix is also logged in the Flix client log file. Reading this logged information, you can see the exact actions Photoshop sends to Flix. Here is an example for a typical action (updating a panel) from Photoshop to Flix from the Flix client log file:

2021-11-17 14:51:17.107] [debug] WebSocketManager.onMessage:: "{\"data\":{\"command\":\"DEFAULT_ACTION\",\"action\":\"UPDATE_ASSET\",\"data\":{\"id\":\"1.2.1.5-1\",\"artwork\":\"/var/folders/47/hwq682557jsb2xyd74r1fpc00000gn/T/flix_1637189476415-520457_0_.FLIXTEMP.psd\"}}}"