What is the proper token?

As per the documentation, any string.

https://www.drupal.org/docs/8/modules/maestro/installation

The UI gives an example... It can be anything that you would use in a url call to run the orchestrator.

Would it make sense to auto-generate one, and then have a message that says it should be changed before deploy?

We could, but it forces the site admin to configuration of the orchestrator...

Seems like the person configuring the workflow could just remember to set the url before they say the workflow is completed, instead of having it be the site admin's task. To me, it seems like an extra step that isn't really needed. It can autogenerate something unique, and then if someone really wants it changed, they can simply change it.

Sorry to say but your explanation in https://www.drupal.org/docs/8/modules/maestro/installation and in the UI at /admin/config/workflow/maestro - is no very satisfying. These explanations don't give any answer which token is meant by.
I tried all kind of tokens and strings and get always the answer: "Wrong Orchestrator Token"
and funny enough when I write just "token" I receive just a white page of death when calling /orchestrator
Are there any example to get an idea which kind of token should be set? - This installation point is really not understandable.
Thanks for any helpful hint about

Orchestrator page runs identically to that of the Drupal cron. It returns a 402 status code. Not a whitescreen.

If you initially looked at the http://yoursite/orchestrator/[[wrong or missing token]] page and "Wrong Orchestrator Token" was shown, and then fix the URL manually to have the right token, your browser is still showing the original page... Run the orchestrator in a new browser window/tab to verify functionality.

Keeping this as postponed for people to verify that in a net-new browser window, with the proper orchestrator URL (as shown above), it works.

@_randy
Yes it works well : no more message Wrong Orchestrator Token. I followed all your process.

Of course like everyone I did activate the strange message after using the Run Orchestra menu item.

1. Create a Token in the Admin page Maestro Engine Module Settings : SITE-URL/admin/config/workflow/maestro
2. Browse to the URL with your Token: SITE-URL/orchestrator/MY-TOKEN
3. Then it is a bit strange because there just nothing happening. There no success message, still no more message Wrong Orchestrator Token. For now I didn't use the trick that you explained here in order to prove that the orchestrator is running, I feel I can follow the Maestro.

Thank you ;-)

I'll add this to the documentation so that this doesn't catch anyone else. Thanks for the review.

Added this information to the documentation on the orchestrator during install.

No there is no way to install maestro. I het somehow crazy what is meant by "token"
As soon as I fill out the MUST field in admin/config/workflow/maestro with any string (as you suggest),
my site crash in white screen of death - I have then to uninstall all maestro modules to make it run again.
Sorry to say, but for the you instruction at https://www.drupal.org/docs/8/modules/maestro/installation
us very very unclear - - please put an example how to fill out http://[site]/orchestrator/{token}
when I write ay string as you suggest eg http://[site]/orchestrator/maestro - the websites crashes
so what is meat by this {token} ???

@ChoY

I don't know why you're getting a White Screen, however, I made this quick video showing how to configure AND test the url.
As per the other comments in this thread, the Orchestrator returns a 204 status, exactly the same thing the Drupal Cron URL does. This produces no output and gives the appearance of a white screen or no change on the browser. This is by design.

Please view this video and test out your orchestrator.

https://www.youtube.com/watch?v=903PUH15_HU

Thanks for the video:
So of I understand now well I can set as {token} any string e.g. "abc" without any additional bracket or slashes
So far so good. I run a drush cache-rebuilt and/or a cron and then I have to call the url http://[site]/orchestrator/abc and the result will be just a white screen (on my firefox config) or a return to the startpage on a standard browser config (I tested it as well with chrome). And then everything is okay as it should be?

I think this is somehow very confusing explained in the maestro documentation, when not looking your video.
It also don't seem to me to make sense. Why I have to configure something that only give me feedback when i have done something wrong (with "Wrong Orchestrator Token") and just no feedback at all, when I have it done right, if not just a white screen or a redirect to my browser startpage? -

Couldn't it not be done easier or better explained?

I am unsure of what the issue still is.

The orchestrator URL runs identically to how Drupal Cron's manual external URL link does. Returns a 204. Drupal Cron's external URL provides zero feedback on successful operation, but will throw errors when issues arise.

For example, this is my Drupal Cron external link
http://mysite/cron/_Kc3ZeecSQERwL3QqqgiRaiqMwhQM7HoFZJ4tU-aW8MDhNWB3i1gX...

When I run it, it gives me a 204, or it will display PHP debugging errors. This is no different than Maestro.

I am unsure of what else to add to help clarify this. This is how the orchestrator was designed to run when using an external URL calling mechanism as you check for return HTTP status to ensure a 204 was returned.

If you want to run the orchestrator manually for testing, that is why we include the option to run it via task console refreshes.

Well for me two thing were unclear:
First what is meant by {token}? - now I know can write any string (e.g, abc or xyz) but without path, bracket or slashes
Second once this is done should run a cache-rebuilt and/or a cron and then call zhe link http://[site]/orchestrator/stringabcxyz
And when there is NO message, just a white screen, everything is fine.

But the current explanation in the documentation doesn't explain nothing about
A a maestro dummy I have to divine what is meant by {token}, and wonder why I get either error message "Wrong Orchestrator Token " or in case I did all well just a white screen - which must me even more believe that I did something wrong.

This is the issue of this discussion "What is the proper token?".
There is simply a need better for a clearer explanation in the documentation
https://www.drupal.org/docs/8/modules/maestro/installation

@ChoY still after many years, a better documentation should be available and right from the setting page. I feel that 100% of users encounter this trouble. This should be avoided for provide a nice user experience for every user.
The error is back on Token // unexpected error.