One useful structure we see people reach for is having customer workloads in one organization, and orchestrators / routers in another. This is a nice separation! But it does hit up against the intentional org boundaries we have in place. One of these boundaries is that fly-replay must target an app in the same org as the source.
This is a bit of a shame, since it would be really nice to fly-replay from your main router to a customer app, across the orgs. So, now you can! (if you want). In your dashboard settings you will find a new Cross-Organization Replay setting where you can configure who is and isn’t allowed to fly-replay across that boundary. If you’re on today’s flyctl release (v0.3.234) you can also manage this with fly orgs replay-sources.
Some more detail and example commands can be found in the Cross-Organization Routing section of the fly-replay docs.