Lime Web Components API Documentation - v7.4.0
    Preparing search index...

    Interface ProblemErrorAlpha

    Technical error details for a problem.

    While Problem.description provides a user-friendly explanation, ProblemError captures the underlying technical details useful for debugging. This separation allows the platform to show appropriate information to different audiences.

    import { Problem, ProblemSeverity } from '@limetech/lime-web-components';

    const problem: Problem = {
        id: 'sync-error-042',
        providerId: 'external-crm-sync',
        type: 'connection-error',
        description: 'Failed to sync deal with external CRM',
        createdAt: '2024-01-15T14:22:00Z',
        severity: ProblemSeverity.High,
        status: 'pending-retry',
        context: { limetype: 'deal', id: 98_765 },
        error: {
            message: 'ETIMEDOUT: connection timed out after 30000ms',
            code: 'ETIMEDOUT',
            stack: 'Error: ETIMEDOUT\n    at TCPConnectWrap.afterConnect...',
        },
    };

    Problem.error

    interface ProblemError {
        code?: string;
        message: string;
        stack?: string;
    }
    Index

    Properties

    code? message stack?

    Properties

    code?: string

    Error code for programmatic handling.

    Codes allow categorizing errors without parsing message text. Use standard codes where applicable (e.g., ETIMEDOUT, ECONNREFUSED) or provider-specific codes.

    message: string

    Technical error message.

    This is the raw error message from the underlying system, which may be more technical than the user-facing Problem.description.

    stack?: string

    Stack trace for debugging.

    The full stack trace helps developers diagnose where errors originated. May be displayed in an expandable "Technical Details" section.

    Settings

    Member Visibility

    On This Page

    Properties