Loading
시스템 관리자에 대한 피싱 방지 MFA 및 전 직원사용자 MFA 적용 안내 더 많이 읽기

Facing UNKNOWN_EXCEPTION error when calling API to retrieve member vouchers.

게시 일자: Jul 10, 2026
상세 설명
When calling the Loyalty Management Connect API endpoint to retrieve member vouchers (GET request), the API returns a 500 status code with the following response body:

"errorCode": "UNKNOWN_EXCEPTION", "message": "We were unable to process your request. Error ID: <error_id>"
 
This behavior has been observed in orgs where:
  • Multi-Factor Authentication (MFA) session security levels are configured on the integration user profile or in org-wide session settings, causing the OAuth/REST API token to fail session security validation at the platform level before reaching the Loyalty Management service layer.
  • The Connected App (or External Client App) has restrictive OAuth or session policies that conflict with Loyalty Management API session requirements.
  • The user's profile or permission set lacks at least Read access to the VoucherDefinition and ProductCategory objects.
  • Custom Apex triggers on the LoyaltyProgramMember object contain unbounded SOQL queries that exceed governor limits under high-volume conditions, producing intermittent failures during member creation.
솔루션
Cause 1: Insufficient Object Permissions on VoucherDefinition or ProductCategory:
  1. Navigate to Setup > Profiles (or Permission Sets) and open the profile or permission set assigned to the integration user.
  2. Select Object Settings > Check for related Loyalty Entites example:
    1. Locate VoucherDefinition and confirm that at least Read access is enabled.
    2. Locate ProductCategory and confirm that at least Read access is enabled.
  3. If either object lacks Read access, enable it and save.
Cause 2: High Assurance Session Security Requirement on User Profile:
  1. Navigate to Setup > Users and identify the integration user making the Loyalty Management API calls.
  2. Navigate to Setup > Profiles and open the identified profile.
  3. Select Session Settings within the profile.
  4. Locate Required Session Security Level for API Access or Session Security Level Required at Login.
  5. Change the value from High Assurance to Standard.
  6. Save the profile changes.
  7. Navigate to Setup > Session Settings (org-wide).
  8. Under Session Security Levels, confirm that the OAuth flow type in use (e.g., Username-Password or JWT Bearer Token) is listed under the Standard category, not High Assurance. Move it to Standard if necessary.
  9. Save the session settings.
Cause 3: Connected App OAuth Policy Misconfiguration:
  1. Navigate to Setup > App Manager.
  2. Locate the connected app used for Loyalty Management API integration and select Manage.
  3. Under OAuth Policies, verify that Permitted Users is set to All users may self-authorize or Admin approved users are pre-authorized with the integration user's profile included.
  4. Confirm IP Relaxation is set to Relax IP restrictions for server-to-server integrations.
  5. Under Session Policies, set High Assurance session required to None.
  6. Save the connected app configuration. Changes may take up to 10 minutes to propagate.
Cause 4: Intermittent Failures During Loyalty Program Member Creation (Governor Limits):
  1. Navigate to Setup > Apex Triggers and identify all triggers on the LoyaltyProgramMember object.
  2. Try review each trigger for unbounded SOQL queries (queries without appropriate WHERE clauses or LIMIT statements).
  3. Try add selective filters to reduce rows returned below the 50,000-row governor limit.
  4. Consider using asynchronous processing (Queueable or Batch Apex) for high-volume operations.
  5. Navigate to Setup > Debug Logs, enable logging for the integration user or action performing user, and reproduce the member creation API call to capture the exact exception.
  6. Review the debug log for System.LimitException or other governor limit violations and refactor the offending code.
Knowledge 기사 번호

005388790

 
로드 중
Salesforce Help | Article