Troubleshooting

while octarender is an extremely robust platform, each render is unique in its composition and issues may arise in this section, we will cover how to diagnose these issues and outline your next steps issues most commonly manifest themselves in the form of errored frames these can be easily identified on the platform, both on the project timeline as well as the frames grid, where they are highlighted with a red indicator tag diagnosing frame errors view error summaries clicking directly on any errored frame card will update the main viewport to display the high level error state (e g , "blender session ended unexpectedly" ), helping you instantly see which frame failed and on which specific worker host inspect detailed logs to diagnose further, click on the logs toggle tab directly underneath the main viewer canvas analyze root causes this action expands the inline task logs terminal layout at the bottom of the dashboard here, you can review the actual execution outputs, memory profiles, and stack traces directly from the remote node container to pinpoint exactly what caused the processing disruption common causes the most common cause of an errored frame is that the hardware node (or nodes) you have rented lacks sufficient system ram or vram to handle the complexity of your blender scene alternatively, an individual provider node may occasionally experience a localized system fault if you encounter an error, use the following isolation steps to get your render back on track step 1 re queue the affected frames select the errored frames directly from your grid or timeline and click the global "requeue" action button at the top of the interface this pushes the tasks back into the network pool step 2 identify the problematic node if the frames fail a second time, you will need to pinpoint the exact worker instance causing the bottleneck click on the specific frame tile that returned an error click the frame info icon on your toolbar layout to open the sidebar this action reveals the frame details panel, which lists the exact node id responsible for executing that specific task block step 3 terminate the node session once you have copied the faulty node id navigate away from the project view and head to the render nodes workspace under render > render nodes locate the matching machine block using the unique node id you identified click the termination action button on that card to drop the lease and stop your active session with that provider our orchestration system will automatically spin down that unit and redirect your outstanding queue items to healthy, capable hardware slots on the network diagnosing failed submission should you experience an issue while trying to pack or submit your project from the addon, you will need to gather your local environment data before contacting support prior to raising a support issue, make sure to capture the direct error logs from inside blender so our team can diagnose the issue quickly how to retrieve blender console logs in blender's top menu bar, navigate to window > toggle system console a command line terminal window will pop open displaying the background processes of the addon highlight and copy the complete text output leading up to the submission failure still experiencing an issue? reach out to our team directly on discord https //discord gg/5xvqwmnsrs or telegram https //t me/octa space when posting your request, please provide a brief description of what you were doing when the failure occurred the verbatim terminal output you copied from your blender system console and octarender logs your uuid any specific error codes or pop up warning messages displayed by the addon interface