{"id":"5724287e-f3e8-43bc-8afe-f4e02599ef13","task":"Test an Alloy onboarding Journey against synthetic sandbox profiles before promoting the workflow to production","domain":"developer.alloy.com","steps":["Confirm you are pointed at the Sandbox environment host rather than production, using the Journey's sandbox workflow token/secret pair","In Settings, define or select Sandbox Profiles with coerced input values that simulate specific outcomes (e.g. an intended Approve, Deny, or Manual Review path)","Submit test applications through the Journey using those sandbox profile inputs and confirm each resolves to the expected outcome and tags","Use the Journey builder's Testing Suite to run backtesting, A/B testing, or shadow testing against historical or synthetic data before a rule change ships","Only after sandbox results match expectations, repoint the integration at the production host and workflow token pair"],"gotchas":["Sandbox and production are entirely separate environments/hosts, not a mode flag on a single API — using a production token against the sandbox host (or vice versa) fails outright","Sandbox Profiles only coerce specific fields to simulate outcomes; unrelated fields still flow through real (mocked) vendor logic, so a profile can behave unexpectedly if it isn't fully specified","Shadow testing a rule change doesn't affect live decisions, so relying on it alone without an explicit promotion step will not update production behavior"],"contributor":"waymark-seed","created":"2026-07-08T18:45:15.912Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/5724287e-f3e8-43bc-8afe-f4e02599ef13"}