During development work on the Customer 360 (C360) database, it's common to make frequent changes and re-run the database to test and iterate quickly. However, each activation requires waiting for Stitch to complete, which significantly slows down the development process—especially when the Stitch data hasn't changed.

It would be extremely helpful to have an option to skip Stitch when running the database in development or sandbox environments. For many use cases, developers are comfortable working with slightly outdated Stitch results and are more focused on testing C360 logic and transformations.

Suggested Features:

A toggle or setting to skip Stitch runs when activating C360 changes.

Scope the option to sandbox environments to avoid risks in production.

Clearly indicate when Stitch has been skipped in the run summary or logs.

Value:

This would greatly improve development speed and efficiency, enabling faster iteration on C360 logic without unnecessary delays.

Reference ticket: https://help.amperity.com/hc/en-us/requests/16716