Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Otter Orchestration Job Trigger - Error 500

    Scheduled Pinned Locked Moved Support
    apiotter
    3 Posts 1 Posters 7 Views
    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.
    • ? This user is from outside of this forum
      Guest
      last edited by

      I have a pretty default install of Otter but with IIS serving the site.

      I have created an orchestration plan that runs a powershell script with pscall, and a template that applies it to localhost. I can trigger the job template manually and it runs (Jobs->Create Orchestration Job), but if I try via the API call it returns "Error creating job: Invalid name.".

      The template is enabled for API calls, I have tried with and without using a key, and I have checked the IIS logs.

      Any idea how I can resolve this or find more info on this error?

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        I think that error means that the plan name is in an invalid format in the job template...

        Can you put together the various screenshots and the method you used to call the API, so we can try to reproduce it, and then submit this as a support ticket?

        1 Reply Last reply Reply Quote 0
        • ? This user is from outside of this forum
          Guest
          last edited by

          Thanks for the pointer. I noticed if I edit the Job Template it doesn't seem to have the right plan 'selected' in the Plan Name dropdown (it defaults to the first in the list every time). I think I saved it without noticing and it ended up attached to the wrong one.

          Maybe review the edit code that generates this page: https://url/job-templates/edit?jobTemplateId=x

          1 Reply Last reply Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • 1 / 1
          • First post
            Last post
          Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation