2026.3.3 workflowname that ends with whitespace
Very minor bug, but if you rename a workflow and you accidentally leave a whitespace as last char, then you can't reach the workflow anymore via the workflow screen (because it links to url without that whitespace) and you get a "not found"
All Comments (2)
another thing I noticed: after renaming the workflows:
the workflows, who were linked to schedule. stopped triggering. the next runtime was correct, but it just didn't happen.
after restarting the service, I noticed that the schedules had an empty workflow. I had to relink that.
Hello Denis,
Thank you for the report and for the follow-up about the schedules.
I looked into both issues and I can confirm the cause of each one.
The first issue happens because PowerShell Universal saves the workflow name exactly as typed, including a trailing space.
The link on the Workflows page drops that space, so the workflow page looks for a name that does not exist and shows "Not Found".
The second issue is related.
A schedule stores the name of its workflow, and renaming a workflow does not update the schedules that point to it.
Until the service restarts, the schedule still fires at the right time, but it cannot find a workflow with the old name, so no job starts.
Each missed run writes a "Workflow <old name> not found." error to the server log.
After a restart, the schedule is no longer loaded for that workflow, which is why it showed an empty workflow.
To fix a workflow name that ends with a space, you do not need to open the workflow page.
Go to the Workflows page.
Click the More Actions (…) menu at the end of the workflow row.
Select Edit Properties, remove the trailing space from the name, and save.
Since this is also a rename, please re-link the schedules of that workflow afterwards, the same way you did before.
To find any schedule that still points to a workflow name that no longer exists, you can run this from a PowerShell Universal script or after Connect-PSUServer:
$workflowNames = (Get-PSUWorkflow).Name
Get-PSUSchedule | Where-Object { $_.Workflow -and $_.Workflow -notin $workflowNames } | Select-Object Id, Name, Workflow
You can then re-link each one with Set-PSUSchedule -Id <Id> -Workflow '<new name>'.
I am reporting both issues to our development team, and I will let you know when a fix is available.
Best regards,
Patrick Ouimet