Yeah, got it to work, had to select one of the jobs first, and then all columns showed :) This is great, I’m really starting to love QUE as much as I do Templater :-)

@pbretz

The jobs being left in a state of “processing” in Google Sheets is actually a bug left over from the way the Google API updates when footage is missing. Technically speaking, the render-status should be changed to “done” in the Google Sheets since it completes the Job with the option set in the Templater Preferences dialog.

This was a scenario we likely should have envisioned in the past, but our assumption was that customers would use Spot Checks rather than the render-status to check for outputs with missing footage.

Either way, we’ll see about implementing some sort of flag to indicate Jobs that complete with missing assets.

Thanks,

Jeff

@pbretz Hi Pete, I checked in and it looks like we’ve got it fairly high on our list, and we’re eyeing early next year for release. I don’t have an exact timeframe, but hopefully in the first few months.

@rkvalvaa

Glad to hear it. If you have any other questions or run into any other issues, please don’t hesitate to get in touch.

Thanks!

@seth thanks. That is what the behavior is. It seems to apply to all filters. I get the same limit with filtering output.

Thanks @seth! Just to be clear on (2), the issue happens when I’m trying to set a filter - ie select a satellite in it’s filter drop down, or try to set an action like reassign selected jobs to another satellite. When I interact with the dropdown, my selection(s) in the dropdown will be cleared if the render-status changes for any job in the campaign before I apply / submit the selection(s).

@surabhiv

At the moment, Templater Bot can only be set up to automate either video production or Spot Checking, so if you’d like to have both actions automated, you’ll need to look into running two separate versions of Templater. There is a Reserved Column that Templater recognizes named bot that will allow you to designate which Bot should process each line of data in your data source. Using this feature, you should be able to route preview actions to one Bot to perform Spot Checks and render actions to another that can do render/replication actions.

@jeff Thanks

@jeff okay thanks