MSX jobs are now excluded from being returned by Get-DbaAgentJob

[tonyfountain]

Verified issue does not already exist?

I have searched and found no existing issue

What error did you receive?

No error, just missing results when using Get-DbaAgentJob to specifically for MSX jobs.

Steps to Reproduce

Get-DbaAgentJOb -SqlInstance '<sqlinstance>' -Job '<name of msx job>'

Please confirm that you are running the most recent version of dbatools

0.10.0.80
2.7.20

Other details or mentions

I see the change was made to support the Sync-DbaAvailabilityGroup cmdlet, but this breaks our current code base of automated installs and setups. We depend on the cmdlet to return the MSX jobs so we can continue our post-configuration scripts. If MSX jobs cannot be used, I feel either the Sync-DbaAvailabilityGroup cmdlet should exclude them, or Get-DbaAgentJob should have a switch to include or exclude MSX jobs. But not unconditionally remove them.

What PowerShell host was used when producing this error

VS Code (terminal)

PowerShell Host Version

Name Value

---

PSVersion 5.1.22621.6345
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.22621.6345
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

SQL Server Edition and Build number

Microsoft SQL Server 2025 (RTM) - 17.0.1000.7 (X64)
Oct 21 2025 12:05:57
Copyright (C) 2025 Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2025 Standard 10.0 (Build 26100: ) (Hypervisor)

.NET Framework Version

.NET Framework 4.8.9310.0

[tonyfountain]

FWIW - I can submit the changes to both cmdlets if it needed.

[tonyfountain]

I believe if this were removed from Get-DbaAgentJob:

# Always exclude MSX jobs (CategoryID = 1) - they cannot be synced to secondary replicas
$jobs = $jobs | Where-Object CategoryID -ne 1

and change this line in Sync-DbaAvailabilityGroup:
$jobsToSync = Get-DbaAgentJob @splatGetJob
to

# Always exclude MSX jobs (CategoryID = 1) - they cannot be synced to secondary replicas
@jobsToSync = Get-DbaAgentJob @splatGetJob | Where-Object { $PSItem.CategoryId -ne 1 }

Should satisfy both scenarios.

[tonyfountain]

If no one objects, I can make time next week and submit the pull request. Just busy this week wrapping up loose ends as I'm leaving Friday to go out of town for the weekend for a pool tournament. I just do not know if there are other pieces of code that might be affected by moving the logic.