Organization contains jobs that are incompatible with the new configuration

[AlexL]

Interesting new issue editing organizations since upgrading to v8.5.
When we edit a organization we get the following error message after pressing the first Next and cannot continue.

"Organization contains jobs that are incompatible with the new configuration. Please edit these jobs beforehand."

So far observed by smaller organizations that just have a single job. Jobs are configured by adding the organization and selecting all (incl Teams posts) not entire organization.

If we run through the edit job wizard, do not change anything, just next next save afterwards the organization can be edited without any problem.

Seems like a bug to me. Happens on multiple different vbo servers/installations with all organizations, so not a single random occurence.

[Mildur]

Hi Alex,

Can you please open a support case when you face such a technical issue?
Please remember that this forum is not the place to ask for bug confirmation (Forum Policies).

Our Support team is trained and has the tools to determine whether something is a bug or not. If it is a known bug, you will receive confirmation and a private fix if available. If it is an unknown bug, the case will be escalated to our R&D teams.

Thank you,
Fabian

[karsten123]

same. as a workaround i changed the selection to whole organization and set it back after edit the organization.
it is definitely a bug and no, i dont want to raise a ticket. thanks!

[AlexL]

Same, resolving the issue with a quick workaround is less work than going thru the effort of creating a ticket. Luckily the +200k licensed users we have currently are concentrated on a relatively low number of large customers rather than a lot of smaller companies or else the pain of the workaround would possible have been bigger. But likely a few lines of powershell code would have resolved the issue in that case.
But interestingly, you don't even need to change something, just doing the edit job wizard and saving it on the end fixes this issue.

[karsten123]

@Alex
interesting. thanks for the information.
i my case it was only for jobs with Teams posts activated.