Thanks for getting in touch.
It looks like you’ve setup everything correctly. Azure Web App targets behave just like regular targets and should be scoped in during your deployment as you expect.
Could you please confirm what version of Octopus you’re running?
We noticed those
PayoutApiTroxy targets are scoped to environments, which I understand has been blurred for privacy reasons. But could you please confirm that the environment you’re deploying to matches one of the environment scopings for your targets?
We can’t see any sort of typo happening with the role between the target and the step, so the environment scopings is the only thing that stands out as a potential candidate.
If you take off the environment scope from one of those targets (I.e. the integration target) and re-run your deployment, does the target then get included?
In terms of it not failing the deployment, could you confirm if your project Deployment Target settings are set to “Deployments with no targets are not allowed”?
To help us get a closer look at your roles, we’ll need to take a look at your raw task log for that deployment, and it would also help if we could see your database tables so we can confirm the role and environment scopings.
We’ve created a private upload location here. Could you please let us know when you’ve uploaded your raw task log and database (.bak) file? This will only be viewed by Octopus staff and deleted immediately after we’ve finished reviewing.