Solved – Orchestrator ‘Unexpected token ” in expression or statement’

Boy oh boy,this is probably the single cause of most of the worlds Orchestrator frustration…and I think we’ve narrowed it down to a solution!

Problem

When running a runbook, you encounter strange error messages like the following.

Unexpected token ‘some string’ in expression or statement

Cause

Orchestrator runs afoul of unescaped quotes marks all the time. Simply put, if you’re running into messages like this one, look at the data in your Orchestrator pipeline for any instances of the following characters