> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/virtual-environments/implementing-virtual-environments/creating-a-master-process-flow/special-considerations-for-building-master-process-flows/special-considerations-for-building-master-process-flows-trigger-settings.md).

# Special considerations for building master process flows - trigger settings

## Introduction

Currently, the [trigger shape](/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape.md) cannot be replaced as part of [virtual environment configuration](/product-documentation/virtual-environments/implementing-virtual-environments/configuring-a-virtual-environment-version.md). As such, you should consider how the trigger settings in your master process flow will operate when run in virtual environments.

{% hint style="info" %}
The ability to replace trigger settings as part of virtual environment configuration will be added soon - please keep an eye on [release notes](/product-documentation/release-information/core-release-notes.md) for upcoming updates.
{% endhint %}

## Schedules

If your process flow needs to run on an automated schedule, does the *same* schedule apply to all virtual environments?

* **Yes**\
  No further action/consideration required - define the required trigger schedule(s) in the master process flow.
* **No**\
  Currently, it's not possible to create different trigger schedules for different virtual environments. As such, you should create different process flows (or different versions of the same process flow) for each required schedule, and deploy the appropriate flow/version to each virtual environment.

## Webhooks & callbacks

When you add/edit a [webhook ](/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape/trigger-shape-webhook.md)or [callback](/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape/trigger-shape-callback.md) URL via the [trigger shape](/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape.md) in a master process flow, you have the option to select a virtual environment - for example:

<div align="left"><figure><img src="/files/UrDE7mYSJdHSlgNLadhv" alt="" width="375"><figcaption></figcaption></figure></div>

When a virtual environment is selected here, any webhook or callback URLs will be generated as required to trigger the process flow in the corresponding virtual environment. For more information, please refer to the following pages:

* [Trigger shape (webhook)](/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape/trigger-shape-webhook.md)
* [Trigger shape (callback)](/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape/trigger-shape-callback.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.wearepatchworks.com/product-documentation/virtual-environments/implementing-virtual-environments/creating-a-master-process-flow/special-considerations-for-building-master-process-flows/special-considerations-for-building-master-process-flows-trigger-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.