Dataclay — Automating Digital Production
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Register
    • Login

    Bot Preferences

    Scheduled Pinned Locked Moved
    Templater Bot Deployment
    2
    3
    476
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ZTH- NUKEundefined
      ZTH- NUKE
      last edited by

      Just updated to AE 2020 with the latest Templator version. I don’t even use the Bot, only Pro but when try to open up Preferences and save anything I get an Error.

      Preferences Save Error
      Templater Bot can queue a max of 20 jobs at any given time. Please adjust and try again.

      I don’t have Bot license so I can’t change these options to begin with. Even if I just open up the preferences window and don’t change anything I get this error. It happens on a new document and in the document I want use templator in. What is the deal here? I have been trying everything with no avail.

      Things I have tired:
      Reinstall AE to different versions
      Reinstall Templator 2 and active
      Sign in/out of google sheets
      Tired local data source - couldn’t get that to work

      I am desperate to find a solution.

      _Zach

      1 Reply Last reply Reply Quote 0
      • Jeffundefined
        Jeff
        last edited by

        @ZTH-NUKE Thanks for getting in touch with us. Could you try resetting your After Effects preferences by following the steps outlined at this link? If that doesn’t make a difference, could you post a copy of your templater.log file? It should be located in the same directory as your AE project file. Hopefully, with that information, we’ll be able to get this issue resolved. Thanks!

        1 Reply Last reply Reply Quote 1
        • ZTH- NUKEundefined
          ZTH- NUKE
          last edited by

          @Jeff - SUCCESS!

          Thank you, that did the trick. I have never had that issue in the past and couldn’t find anyone or documents explaining the issue.

          Thank you again. We are up and running.

          -Zach

          1 Reply Last reply Reply Quote 0
          • First post
            Last post