What is a rundown bundle?
A rundown bundle is a diagnostics export generated directly from the Cuez Automator, saved as a .cuezbundle file. It collects everything about that Automator instance that we would otherwise ask for as separate log files. For example, it contains the app version, the connected devices, step buttons, automations, macros, variables, and more, this for the loaded rundown from the moment it connected. The most recent system logs are also included.
The bundle is built so that, on our end, we can try to reconstruct the issue locally first, without needing access to your (Cuez) rundown, and without a screen-share or remote session.
Why we ask for a rundown bundle
When we ask for a rundown bundle, it's because we need to see the exact configuration and logs behind an issue rather than relying on a description or a screenshot alone. It lets us compare a working block, macro, or device against a failing one, check connection and timing logs around the moment something went wrong, and confirm whether a setting is misconfigured or whether we're looking at a product bug.
Screenshots show us what a panel looks like right now. They don't show us the underlying values behind a function's parameters, whether a section is quietly disabled, what the device connection log said in the seconds before a drop, or what was actually sent during a rundown sync.
How to generate a rundown bundle (.cuezbundle)
From within a loaded Episode/rundown in the Automator:
Click the gear icon in the top right corner.
Select 'Project settings' from the dropdown.
Select the 'Diagnostics' tab.
Click 'Export rundown bundle' and save the file.
Note: the 'Diagnostics' tab is a newer addition to the Automator. If you don't see it under Project settings, update to a newer release from https://download.cuez.app/automator/ first.
Important: the rundown bundle can contain device credentials. Only share it with Cuez support, never post it anywhere public.
How to send us a rundown bundle (.cuezbundle)
Please send the rundown bundle (the .cuezbundle file) through a chat conversation (blue dot in the bottom right corner of the Automator). You can add it as an attachment, the same way you'd attach a screenshot.
Ideally, we'd always receive the bundle alongside a description of what's happening, so also add any other information or description about the issue as usual; the bundle is additional evidence, not a replacement for the conversation.
What else helps us
The rundown bundle covers configuration and logs, but a few extra things speed up the investigation considerably:
The name of the specific block, macro, button, or device involved — for example "the CLIP block" or "the ATEM device", especially if there's more than one item with a similar name in the rundown.
A working example to compare against, if only some blocks/items/devices are affected and others aren't. Telling us "it works on the CLIP block but not on GRAPHIC", for example, lets us diff the two directly.
The approximate time the issue occurred, if it's a one-off (a device dropping, a rundown not syncing) rather than something reproducible on demand. This lets us find the right moment in the logs instead of scanning hours of output.
A screenshot of the relevant configuration panel (the automation steps, the device config, the CuezDeck button,...), so we can see what you're seeing alongside the raw data in the bundle.
The Automator version you're currently running, if not already visible in the bundle, shown at the bottom of the Automator window or via 'Project settings' from the dropdown under the gear icon.
An exported Event Log, especially if the issue is reproducible. Open the Event Log from the 'bell' icon in the left sidebar, reproduce the issue, then check the 'Events' and 'Traces' tabs for the trigger in question. Export it directly as a JSON or CSV file and attach that to your message, alongside the .cuezbundle file. This lets us confirm our diagnosis against what actually ran, rather than just against the configuration. See How can I use Traces and the Event Log in the Automator? for the full walkthrough.
Important: if you've already tried a fix and it didn't work, please generate a fresh rundown bundle after making the change, rather than sending the original one again. This can help confirm whether the fix actually applied.