Business Central keeps the last error a user hit: open Help & Support from the question mark and choose View the last known error to see the error text, code and AL call stack. It only works in the same session, so for anything going to your partner, copy the error details from the dialog itself and add the session IDs, timestamp and context.
The one-sentence answer
Choose the question mark in the top-right corner, open Help & Support, and select View the last known error in the Troubleshooting section; the user who hit the error must do this in the same session, and for a partner ticket the Copy error details text from the original dialog is still the better evidence.
Pontos-chave
- In Business Central, View the last known error in the Troubleshooting section of the Help & Support page opens the Latest Error page (page 9180), which shows Error Text, Error Code and Error Callstack.
- The Latest Error page reads the last error of the current session only, so an administrator cannot see another user's error there and the information is lost once the user signs out.
- Since Business Central 2024 release wave 1 (version 24), error dialogs have a Share details menu with Copy error details, Share details via Teams and Share details via email.
- Copied error details contain the Application Insights session ID, a UTC timestamp, the user telemetry ID and the AL call stack, which together let a partner find the exact session in telemetry.
- For errors of other users or past sessions, use the Telemetry tab in the Business Central administration center or event RT0030 in Application Insights, and assign a Telemetry ID to every user.
Four places an error leaves a trace
“I got an error” is the most common support request we receive and the least useful one. Before anyone can diagnose it, someone has to recover what actually happened. Business Central offers four sources, and each answers a different question for a different person.
1. The error dialog
Who: the user, at the moment it happens
Share details copies the message, session IDs, UTC timestamp and AL call stack. The most complete evidence, but only while the dialog is open.
2. Latest Error page
Who: the same user, same session
Reached from Help & Support. Shows error text, error code and call stack after the dialog has been closed.
3. Job Queue Log Entries
Who: admins, for background work
Background sessions show no dialog. The log entry keeps the error, and Show Error Call Stack displays where it failed.
4. Telemetry
Who: admins and partners, afterwards
The admin center Telemetry tab and Application Insights record error dialogs (event RT0030) for every user, long after the session has ended.
How to open “View the last known error”
- Choose the question mark in the top-right corner (or press Ctrl+F1) to open the Help pane.
- Select Help & Support. Every company in every environment has this page.
- Scroll to the Troubleshooting section and select View the last known error.
- The Latest Error page opens with three fields: Error Text (what the user saw), Error Code (an untranslated technical code) and Error Callstack (the chain of AL objects and lines that led to the failure).
The Latest Error page is page 9180 and is also searchable by name, so a user can type Latest Error in the search box instead of going through Help & Support. The Troubleshooting section additionally shows the Business Central version and the Microsoft Entra tenant ID, and links to page inspection.


Why it sometimes shows nothing, or the wrong error
The Latest Error page does not read a log table. In Microsoft’s source it simply calls the AL functions GetLastErrorText, GetLastErrorCode and GetLastErrorCallStack when it opens. Those functions return the last error of the current session. If there is none, the page says “No errors have occurred since you last logged in”. That design explains every surprise we see:
- An administrator cannot open another user’s last error. Opening the page from your own session shows your own last error, not the user’s.
- Signing out loses it. A new session starts with a clean slate, so ask the user to check before closing the browser.
- It may show a different error. Errors that code deliberately catches, for example with
if Codeunit.Run(...) thenor a try function, also become the “last error”, even though the user never saw them. Microsoft’s own code callsClearLastErrorin places for exactly that reason. - Platform errors are not covered. Microsoft documents that the link shows errors generated by application code (field validation, posting routines, business logic), not errors generated by the platform.
- Collectable errors are unreliable here. When code collects errors and shows them together at the end, the page cannot be relied on to reproduce the exact messages, as Yun Zhu points out.
The error dialog: copy before you close
The dialog itself carries the best evidence, and its design has changed three times. Up to version 21 it had a How to report this issue part with Copy information to clipboard. Version 22 (2023 release wave 1) replaced that with a Copy details action. Since version 24 (2024 release wave 1, generally available 1 April 2024) error dialogs have a Share details menu, and inline validation errors a share icon, offering Copy error details, Share details via Teams and Share details via email. The Teams and email options copy the details and add a link to the page where the error occurred; you still paste the details yourself.

The copied text starts with “If requesting support, please provide the following details to help troubleshooting:” followed by the message and these fields:
Internal session ID
Used by Microsoft support if the case is escalated.
Application Insights session ID
Stored as operation_Id in telemetry; the key to everything the session did.
Client activity id
Also used by Microsoft support for escalations.
Time stamp on error
Date and time in UTC, not local time.
User telemetry id
Matches the Telemetry ID on the User Card.
AL call stack
Object, method, line, app and publisher for each step in the stack.
Read the call stack from both ends. The bottom line is where execution started, so it tells you what the user was doing. The top line is where the error was raised. The publisher on each line tells you whose code is involved: Base Application by Microsoft points one way, an AppSource or partner app another. Since version 27, the error details also include the app version, which Yun Zhu highlighted as useful when an AppSource extension has not been updated.
For administrators: other users’ errors and past errors
When the user has already signed out, telemetry is the only route back. In the Business Central administration center, the Telemetry tab lets you pick a Timestamp, a Time Window in minutes (negative values look backwards), a Query Category and the Environment. The default window is the five minutes before now, so set it around the time the user reported.
With Application Insights enabled, every error dialog emits event RT0030 (“Error dialog displayed”) with the AL stack trace, object, app name and version, company and client type. Two details matter. The message in alErrorMessage is only logged when the developer used a Label or TextConst; and since version 22, alEnglishLanguageDiagnosticsMessage holds the English text, whatever language the user works in. Given the Application Insights session ID from the copied details, Microsoft’s sample query replays the session:
traces
| where timestamp > ago(1d) // adjust as needed
| where operation_Id == '<Application Insights session ID>'
| project timestamp, message,
eventId = customDimensions.eventId, customDimensions
| order by timestamp ascTo trace errors back to a person, each user needs a Telemetry ID on the User Card (Set field to random GUID). Microsoft recommends assigning one to all users so that past situations can be analysed. For a problem that is hard to pin down, the Help & Support page also lets a user switch on more logging for the session before reproducing the issue.
For developers: the AL functions behind it
The same functions are available in your own code, typically after a protected call:
ClearLastError();
if not Codeunit.Run(Codeunit::"My Posting Step") then
LogFailure(GetLastErrorText(), GetLastErrorCode(), GetLastErrorCallStack());GetLastErrorTextreturns the message translated into the user’s language;GetLastErrorCodeis not translated, which makes it the better value to branch on.GetLastErrorCallStackdoes not return every call for some errors, such as divide-by-zero and overflow. Use the debugger with break on errors for those.- Call
ClearLastErrorbefore the protected call, and again after you have handled an expected failure, so the Latest Error page is not polluted with errors the user never saw.
What to send your partner
A good ticket lets the partner start in telemetry or a sandbox within minutes instead of exchanging three emails first. This is the sequence we ask our own customers to follow:
- The complete copied details, pasted as text rather than a cropped screenshot, so IDs and the call stack survive.
- Environment and company. Since version 24, the Report a problem section of Help & Support has a Copy the text below action that copies the Entra tenant ID, environment name and type, client and server session IDs, and the user telemetry ID.
- What you were doing: page, document or record number, the action you chose, and whether it worked yesterday.
- Whether it repeats for other users, other records or in a sandbox.
- If the dialog was closed, the Latest Error page contents from the same session, plus the approximate local time so telemetry can be searched.
Partners can publish their support contact in the administration center under Support > Manage Support Contact, and it then appears in Help & Support for online customers with a paid subscription. If yours is not there, ask for it. Our Business Central support service works from exactly this information.
Common mistakes
- Closing the dialog and signing out before anything was copied.
- An admin opening Latest Error in their own session to “check the user’s error”.
- Sending a phone photo of the screen instead of the copied text.
- Reporting local time as if it were the UTC timestamp in the details.
- Leaving users without a Telemetry ID, so past errors cannot be tied to anyone.
- Reading only the top of the call stack and blaming the wrong app.
Set it up once
Teach key users the single habit of Share details → Copy error details, assign a Telemetry ID to every user, connect the environment to Application Insights, and make sure your partner’s contact details appear in Help & Support. Each takes minutes, and together they turn “it gave an error” into a ticket that can be resolved the same day.
Want errors resolved, not bounced back?
We read the call stack and telemetry, reproduce the issue in a sandbox, and tell you whether the cause is setup, data, an extension or Microsoft.