Hello!
We use project invoice proposal workflow to submit and review/approve project invoices. It is a very simple workflow - one approval step that goes to a user group with one automatic approval action if submitted by a specific user.
After the 10.0.45 update, our UK legal entity is getting this error, when submitted by any user, including sysadmin users.
24/02/2026 18:05:16:
Stopped (error): X++ Exception: Stack trace: Cannot run form on non interactive session.
at SysWorkflowWorkItem-create
SysWorkflowWorkItem-createWorkItems
SysWorkflow-save
SysWorkflowQueue-resume
There is nothing custom about the workflow, it is OOB. There shouldn’t be any forms being called, which is what I’ve seen others mention when the interactive session error has come up.
I’ve rebuilt the workflow from scratch with the same result.
We have another US legal entity that uses the project invoice proposal workflow - it does not have an approval step - it checks for valid data and auto approves or rejects based on criteria. It is NOT having this same issue.
Any suggestions would be greatly appreciated.
Hi @Margie_Paetzold
That error usually means that something in the workflow is trying to open a form while running in a batch (non-interactive) session, which isn’t allowed, and 10.0.45 seems to be stricter about this.
Since your US entity (auto-approve only) works and the UK one has a manual approval step, I’d focus on the approval part. Even if the workflow is OOB, something around the work item creation, notification, or a small extension could be triggering a form call.
I’d suggest:
-
Check that workflow batch processing is running correctly
-
Compare UK vs US approval setup (user group, notifications)
-
Temporarily remove the approval step in UK and test; if it works, you’ve isolated it
Likely something approval-related that the update is now enforcing more strictly.
1 Like
Thank you for this information!
It’s definitely an issue with creating a workflow task/assignment - I changed it from an approval step to a manual decision and it stops at the point where the manual decision step should be assigned to a user.
The “form” would be the workflow assignment option - does this seem like a MSFT bug that needs reported? I’m not sure how to trace it in my UAT and PROD environments since they’re MSFT hosted. I tried searching the known issues and didn’t see anything currently in there.
Our process requires an approval step before invoice proposals are posted.
I appreciate your help!
1 Like
No I completely understand. I’m not in the position to make those decisions for our business however. We have reached out to MSFT because we do believe this is a MSFT bug. I’ll post a response if it ends up being that or something else once MSFT takes a look. I appreciate your help!
That makes sense. I hope Microsoft resolves the issue soon. If not, feel free to let me know, I’ll be happy to help.
