web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

Performance issue when validating Account No. / Account Type on General Journal Line pages

(1) ShareShare
ReportReport
Posted on by 2
Hi Microsoft Support Team,
We are currently experiencing a performance issue in Business Central related to journal entry processing.
Issue Description
When users input or modify values in the following fields:
  • Account No.
  • Account Type
on pages where General Journal Line is used as the source table, the system responds very slowly.
Investigation Result
We performed debugging and identified that the delay seems to be related to the Workflow Management codeunit.
Specifically, the following procedure is consuming significant processing time during field validation:
FindWorkflowStepInstanceWithOptionalWorkflowStart
This procedure appears to be triggered repeatedly whenever the Account No. or Account Type fields are validated.
Current Impact
  • Slow user experience during journal entry input
  • Significant delay when entering multiple journal lines
  • Users report lag during daily operations
Additional Information
  • Environment: SaaS
  • Business Central Version: 27.5
  • Workflow Enabled: Yes
  • Customization related to journal/workflow: No (we already uninstall all extension)
Could you please help advise:
  1. Whether this is a known issue
  2. If there are any hotfixes or performance recommendations
  3. Whether this behavior is expected by design
Thank you for your support.

 
I have the same question (0)
  • Suggested answer
    Grigorios Mavrogeorgis Profile Picture
    1,784 Super User 2026 Season 1 on at
    HI,
    Your investigation points to the right place. FindWorkflowStepInstanceWithOptionalWorkflowStart appears to be triggered during field validation, to check if any active workflow step should react to that field change. On General Journal Line this seems to fire per field per line, so entering many lines multiplies it and the lag becomes very visible.
    Few things to check. Even if you uninstalled custom extensions, the standard Workflow still runs if any enabled workflow listens on journal or general events. Open the Workflows page and check for an enabled workflow with an entry point related to general journal or approval — disable the ones you do not actually use, because the subscribers stay active as long as a workflow is enabled.

    Best test is to run the same journal in a clean sandbox with all workflows disabled. If it is fast there, it confirms the workflow part is the cause, not the journal itself. Since this is SaaS 27.5, capture the slow operation in Application Insights and open a Microsoft support case with that telemetry, so they confirm if it is by design or a regression.

    Hope this help, Best regards.
    ✅ Tick the checkbox below to mark the answer as verified, if it helped resolve your question.
     
    Regards
    Gregory Mavrogeorgis
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,140 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,362 Super User 2026 Season 1

#3
AndrewThomas81 Profile Picture

AndrewThomas81 1,216

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans