Default workflow environment not being used

@CWhite Update: I confirmed with the Workflows eng team that this isn't a bug - The webhook trigger has a specified default environment that can be configured. (see screenshot) Your comment here initially seemed related to a separate bug but I was mistaken on that.

When a workflow is calling another workflow, the child workflow will run in the same environment that the parent workflow is running in (which could be different from the environment the parent workflow was deployed in, for example if passing in a different environment in the webhook url).

This part of your original post may be the key here!

maybe my expectations are not correct around this feature but it seems like it should be clear(er) what the default environment is for a workflow when this param is not supplied.

I've conveyed this feedback internally and can keep you updated here if we release updates to make this a bit clearer! Thank you for surfacing :bow: