Troubleshoot errors with the GoMeddo Log

The GoMeddo Log stores errors that happen in GoMeddo, so you and GoMeddo support can see what went wrong and why without having to reproduce the problem. This page explains where to find log records, how to read them, and how to control what GoMeddo logs and how long it keeps it.

What is the GoMeddo Log?

The GoMeddo Log is a custom object (B25__Log__c) that holds one record per logged event. GoMeddo writes these records in the background, separately from the action that failed. So a log record is kept even when the action itself is rolled back. For example, when a reservation can't be saved, the reservation is not created, but the error is still logged.

Logging never blocks or breaks the action being logged. If GoMeddo can't write a log record, the original action carries on as normal.

Log records appear a few seconds after the event, because they're written in the background. The Logged At field shows when the event happened, which can differ slightly from Created Date.

View log records

1. Click the App Launcher.

2. Search for GoMeddo Logs and select it.

3. Select the All list view.

4. Click a record to see its full details.

The All list view shows the most useful columns: Severity, Source, Operation, Correlation Id, Message, and Logged At. To show a GoMeddo Logs tab in your GoMeddo app, add it in Setup > App Manager.

Read a log record

GoMeddo fills in these fields. The B25 Admin permission set lets users view all log records but not edit or delete them.

When you contact support@gomeddo.com about an error, include the log record's Message, Correlation Id, and Transaction Id. This lets support find the cause without asking you to reproduce the problem.

Configure logging

Three settings control logging. All three work out of the box with their defaults, so you only need to change them when you want more detail or a different retention period.

1. Go to GoMeddo Settings > GoMeddo Setup > System Settings.

2. In the General section, find the log settings.

3. Change the settings you need.

4. Click Save.

The new values apply to actions that start after you save.

How log retention works

GoMeddo schedules a nightly job, Job_PurgeLogs, that deletes log records older than Log retention (days). GoMeddo schedules it automatically when you install or upgrade the package, in production and in sandboxes. You can see it under Setup > Scheduled Jobs. Don't delete this job, otherwise log records are never cleaned up and keep using data storage.

If you deleted the job by accident, reinstalling or upgrading GoMeddo schedules it again.

Write to the GoMeddo Log from your own code

Developers can write entries to the GoMeddo Log from custom Apex, so errors in your own automation appear next to GoMeddo's. Entries follow the same Log level and payload settings.

Use B25.Logger.fromException to build an entry from an exception, B25.Logger.log to add it, and B25.Logger.flush at the end of your transaction to write any buffered entries. GoMeddo writes errors right away; warnings and info entries are kept until you call flush, so call it in a finally block.

global with sharing class MyReservationAutomation {
    global static void run(List<B25__Reservation__c> reservations) {
        try {
            // Your logic here.
        } catch (Exception ex) {
            B25.LogEntry entry = B25.Logger.fromException(ex);
            entry.source = 'MyReservationAutomation';
            entry.operation = 'run';
            B25.Logger.log(entry);
            throw ex;
        } finally {
            B25.Logger.flush();
        }
    }
}

B25.LogEntry has these fields you can set:

To check the settings before doing expensive work, use B25.Logger.isEnabled() (false when Log level is NONE) and B25.Logger.isPayloadEnabled().

If your package must not depend on GoMeddo being installed, call the log through B25.LoggerCallable instead. It accepts the actions log, flush, isEnabled, and isPayloadEnabled. For log, pass the B25.LogEntry field names as keys, with severity as a string.

Type loggerType = Type.forName('B25', 'LoggerCallable');
if (loggerType != null) {
    System.Callable logger = (System.Callable) loggerType.newInstance();
    logger.call('log', new Map<String, Object>{
        'severity' => 'ERROR',
        'source' => 'MyPackage',
        'message' => 'Could not sync the reservation.'
    });
    logger.call('flush', null);
}