This document is generated from the canonical error and warning definitions in sonorancad/core/logging.lua. If a code changes there, this file should be updated to match.
Each entry includes:
Key: internal identifier used in codeCode: support-facing error code shown to users/logsMeaning: what the error or warning is telling youPotential Fix: the first thing to check or change
Warnings use a WRN-* prefix. Errors use an ERR-* prefix. Some warning-level log paths still intentionally reference ERR-* codes when the condition represents a real support issue even if the integration can keep running.
Key:STEAM_ERRORMeaning: SonoranCAD is configured to use Steam identifiers, but the FXServer Steam Web API key is missing.Potential Fix: Setsteam_webapiKeyin your server configuration or switchprimaryIdentifieraway fromsteam.
Key:PORT_MISSING_ERRORMeaning: The configured CAD server entry could not be found for the activeserverId.Potential Fix: Verify theserverIdinconfig.json/convars and confirm that the same server exists in the CAD server list.
Key:PORT_CONFIG_ERRORMeaning: The game server port does not match the port configured in CAD.Potential Fix: Align the FXServernetPortwith the CAD server entry, or allow the integration to auto-correct the CAD entry.
Key:MAP_CONFIG_ERRORMeaning: The live map port configured in CAD does not match the server configuration.Potential Fix: Update the CAD map/listener port for the affectedserverIdso it matches the actual server port.
Key:PORT_OUTBOUND_ERRORMeaning: The detected outbound IP does not match the configured CAD IP.Potential Fix: Update the CAD server IP/outbound IP settings to the actual public IP used by the server.
Key:PORT_OUTBOUND_MISMATCHMeaning: SonoranCAD detected an IP mismatch between runtime networking and CAD configuration.Potential Fix: ReviewmapIp,outboundIp, anddifferingOutboundin the CAD server entry and correct them.
Key:CONFIG_ERRORMeaning: The core configuration could not be loaded or parsed.Potential Fix: Ensuresonorancad/configuration/config.jsonexists, is valid JSON, and is not accidentally named something likeconfig.json.json.
Key:API_ERRORMeaning: The integration could not retrieve version information from the CAD API.Potential Fix: Check the API key, community ID, outbound connectivity, and SonoranCAD API status, then restart the resource.
Key:ERROR_ABORTMeaning: Startup was aborted because one or more critical errors were encountered.Potential Fix: Review earlierERR-*entries in the console/log buffer, correct the first critical failure, and restart the resource.
Key:PLUGIN_DEPENDENCY_ERRORMeaning: A submodule was enabled but one of its required dependencies was not loaded.Potential Fix: Install/start the missing dependency resource or disable the submodule that requires it.
Key:PLUGIN_VERSION_MISMATCHMeaning: A submodule requires a newer version of another plugin/resource than is currently available.Potential Fix: Update the named plugin/resource to the required version or disable the dependent submodule until versions match.
Key:PLUGIN_CONFIG_OUTDATEDMeaning: A submodule configuration file is older than the current template version.Potential Fix: Compare your local submodule*_config.luaversion against the required*_config.dist.luaversion, copy over the missing settings, then restart the submodule.
Key:PLUGIN_CORE_OUTDATEDMeaning: A plugin requires a newer SonoranCAD core than the one currently installed.Potential Fix: Update the SonoranCAD core resource to the required version.
Key:CUSTOM_POSTALS_FILE_NOT_FOUNDMeaning: The configured custom postals file could not be found.Potential Fix: Place the referenced file in the expected postals directory or update the config to point to the correct filename.
Key:POSTAL_RESOURCE_MISSINGMeaning: The configured postal resource name does not exist on the server.Potential Fix: Correct the resource name in config or install the missing postal resource.
Key:POSTAL_RESOURCE_STOPPEDMeaning: The postal resource exists but is not started.Potential Fix: Add the postal resource to your startup config and ensure it starts before players connect.
Key:POSTAL_RESOURCE_BAD_STATEMeaning: The postal resource is present but in an invalid/bad runtime state.Potential Fix: Inspect that resource for startup errors, fix them, and restart it before starting SonoranCAD features that rely on it.
Key:POSTAL_FILE_READ_ERRORMeaning: SonoranCAD could not read the configured postal data file.Potential Fix: Verify the file exists, is readable by the server process, and is valid for the selected postal mode.
Key:POSTAL_CUSTOM_RESOURCE_FILE_ERRORMeaning: A custom postal resource did not expose the expected postal file metadata.Potential Fix: Add the expectedpostal_filemetadata to that resource’sfxmanifest.luaor use a supported postal resource.
Key:IDCARD_RESOURCE_NOT_STARTEDMeaning: Thesonoran_idcardresource is installed but not running.Potential Fix: Useexec sonorancad.cfgand make suresonorancad.cfgcontainsensure sonoran_idcardbeforeensure sonorancad.
Key:IDCARD_RESOURCE_MISSINGMeaning: Thesonoran_idcardresource could not be found.Potential Fix: Use the bundledsonorancad.cfg, confirm it containsensure sonoran_idcard, and install the resource with the exact namesonoran_idcard.
Key:IDCARD_RESOURCE_BAD_STATEMeaning: The ID card resource exists but is not in a usable runtime state.Potential Fix: Useexec sonorancad.cfg, confirm it containsensure sonoran_idcard, and fix the startup errors reported bysonoran_idcard.
Key:INCORRECT_WKWARS2X_VERSIONMeaning: The installedwk_wars2xresource version is incompatible with this integration.Potential Fix: Replace it with the supported version from Sonoran Software’s repository.
Key:CAD_API_DISABLEDMeaning: API sending is disabled by configuration or a runtime toggle.Potential Fix: Re-enable API sending in config/convars or stop using features that require outbound CAD API requests.
Key:UPDATE_CHILD_PERMISSIONMeaning: Auto-update failed because FiveM child-process permission was not granted.Potential Fix: Runexec sonorancad.cfgor add the required child-process ACE/permission for SonoranCAD’s updater.
Key:INVALID_API_MODEMeaning: The configured SonoranCAD API mode was invalid and the resource fell back to production.Potential Fix: Setmodeto a supported value such asproductionordevelopment.
Key:FILE_WRITE_FAILEDMeaning: The resource failed to write a required file to disk.Potential Fix: Check folder permissions, available disk space, and whether the target path is writable by the server process.
Key:CAD_API_REQUEST_FAILEDMeaning: A request to the SonoranCAD API failed.Potential Fix: Check the related support ref, then verify API key, community ID, payload validity, network connectivity, and CAD API availability.
Key:TABLET_RESOURCE_NOT_STARTEDMeaning: Thetabletresource is installed but not running.Potential Fix: Useexec sonorancad.cfgand make suresonorancad.cfgcontainsensure tabletbeforeensure sonorancad.
Key:TABLET_RESOURCE_MISSINGMeaning: Thetabletresource could not be found.Potential Fix: Use the bundledsonorancad.cfg, confirm it containsensure tablet, and install the resource with the exact nametablet.
Key:TABLET_RESOURCE_BAD_STATEMeaning: Thetabletresource exists but is not in a usable runtime state.Potential Fix: Useexec sonorancad.cfg, confirm it containsensure tablet, and fix the startup errors reported bytablet.
Key:LOCAL_NETWORK_TIMEOUTMeaning: The local server network timed out while connecting to SonoranCAD.Potential Fix: If you are seeing this routinely, contact your server host. The network may be overwhelmed or experiencing degraded performance. This suggests your FiveM server is getting timeouts and connection drops.
Key:LOCAL_NETWORK_CONNECT_TIMEOUTMeaning: The local server connection to SonoranCAD timed out.Potential Fix: If you are seeing this routinely, contact your server host. Check the server host, firewall, proxy, or upstream network connection for connection setup delays or blocked outbound traffic.
Key:UNHANDLED_SERVER_ERRORMeaning: An unexpected server-side error occurred and was normalized into a generic coded failure.Potential Fix: Use the support ref in the logs to find the exact exception details and fix the underlying code path or bad input.
Key:UNHANDLED_WARNINGMeaning: A warning occurred that did not map to a more specific registered error code.Potential Fix: Review the warning text and support ref in logs; usually this indicates degraded behavior rather than a full failure.
Key:INVALID_COMMAND_ARGUMENTMeaning: A command was called with missing or invalid arguments.Potential Fix: Re-run the command with the documented arguments, or update the calling script/UI if it is sending malformed parameters.
Key:FEATURE_UNAVAILABLEMeaning: The requested feature cannot be completed in the current state.Potential Fix: Confirm required caches, resources, and dependent subsystems are available, then retry.
Key:MALFORMED_PAYLOADMeaning: SonoranCAD received incomplete or invalid structured data.Potential Fix: Validate the event payload, HTTP body, or NUI/client request that triggered the error.
Key:PERMISSION_DENIEDMeaning: The user or command source does not have permission for the requested action.Potential Fix: Grant the necessary ACE permission or disable the permission gate for that feature if appropriate.
Key:CLIENT_RUNTIME_ERRORMeaning: A client-side runtime or NUI/browser-side error was caught and sanitized before it could dump raw error details to the player console.Potential Fix: Check the matching support ref in the server/client logs, then verify the affected UI/runtime dependency is loaded and the triggering state is valid.
Key:PLAYER_NOT_LINKEDMeaning: The player does not have a linked CAD account.Potential Fix: Run the configured link command, complete the link flow, and verify the link exists in CAD.
Key:PLAYER_NOT_ONLINEMeaning: The player is linked but not currently logged into a CAD unit/profile.Potential Fix: Log into an eligible CAD profile before using the feature.
Key:PLAYER_NOT_IN_CADMeaning: The player must be both linked and active in CAD before the feature can be used.Potential Fix: Link the account first, then log into a valid CAD character/unit.
Key:SUPPORT_INVALID_IDMeaning: The provided support upload/request ID was invalid.Potential Fix: Use the correct numeric support request ID from Sonoran support.
Key:SUPPORT_UPLOAD_FAILEDMeaning: Support logs could not be uploaded.Potential Fix: Retry the upload, then verify outbound API access and the validity of the support request ID.
Key:SUPPORT_UPLOAD_SUCCESSMeaning: Support logs were uploaded successfully.Potential Fix: No action required; provide the generated support reference and upload context to support if requested.
Key:SMARTSIGNS_PLAN_REQUIREDMeaning: Smart Signs authentication failed because the CAD community does not have access to the required Smart Signs feature or plan.Potential Fix: Verify the CAD community has the required Smart Signs access or subscription, then retry Smart Signs authentication.
Key:SMARTSIGNS_AUTH_FAILEDMeaning: Smart Signs authentication failed because SonoranCAD could not authorize the configured community/server.Potential Fix: Check the SonoranCAD API key, community ID, and server ID configured for the Smart Signs resource.
Key:SMARTSIGNS_HELPER_STARTEDMeaning: Thesmartsigns_sonoran_helperresource was started directly, but it is only intended for Smart Signs internal update handling.Potential Fix: Removeensure smartsigns_sonoran_helperorstart smartsigns_sonoran_helperfrom the server startup config and start only the main Smart Signs resource.
Key:BODYCAM_FORCEOFF_PERMISSIONMeaning: The user attempted to use the bodycam force-off command without permission.Potential Fix: Grant the configured bodycam force-off ACE permission to the appropriate staff group.
Key:BODYCAM_CHILD_PERMISSIONMeaning: Bodycam recording could not start because child-process permission was missing.Potential Fix: Add the required child-process permission or use the bundledsonorancad.cfgpermissions.
Key:BODYCAM_F8_PERMISSIONMeaning: The bodycam keybind commands are blocked by ACE permissions.Potential Fix: Allowcommand.SonoranCAD::bodycam::Keybindandcommand.SonoranCAD::bodycam::RecordingKeybindfor the intended player group.
Key:BODYCAM_NOT_ON_DUTYMeaning: The player must be online in CAD before toggling bodycam.Potential Fix: Log into CAD duty first, then toggle bodycam again.
Key:BODYCAM_UPLOAD_TOKEN_INVALIDMeaning: The bodycam upload token was rejected or expired.Potential Fix: Refresh the upload configuration from the server, verify the API auth context, and retry the upload.
Key:BODYCAM_UPLOAD_INIT_FAILEDMeaning: Bodycam upload setup failed before file chunks could be accepted.Potential Fix: Check temp file creation, upload parameters, and server write permissions.
Key:BODYCAM_UPLOAD_CHUNK_FAILEDMeaning: A bodycam upload chunk could not be appended to the target file.Potential Fix: Check disk permissions, disk space, and whether the temporary recording path is writable.
Key:BODYCAM_UPLOAD_INCOMPLETEMeaning: The upload completed request arrived before all expected chunks were received.Potential Fix: Retry the upload and inspect client/network interruptions that may have dropped chunks.
Key:BODYCAM_TURN_FAILEDMeaning: TURN credentials for bodycam streaming could not be retrieved.Potential Fix: Verify the CAD API is reachable, the API key is valid, and TURN-related config overrides are correct.
Key:BODYCAM_RECORDINGS_UNWRITABLEMeaning: The bodycam recordings directory could not be written by the server process, so upload setup or clip finalization could not save the recording file.Potential Fix: Setsonorancad/submodules/bodycamand itsrecordingsdirectory to permission mode777, then retry the upload.
Key:BODYCAM_RECORDING_ACTIVEMeaning: A start-recording request was ignored because a recording was already in progress.Potential Fix: Stop the active recording before starting another one, or debounce duplicate start requests in the caller/UI.
Key:BODYCAM_RECORDING_BLOCKEDMeaning: Bodycam recording was blocked by privacy override or invalid runtime state.Potential Fix: Remove the privacy override or restore the bodycam/stream state required for recording.
Key:BODYCAM_RECORDING_INACTIVEMeaning: A stop or cancel request was made when there was no active recording to stop.Potential Fix: Start a recording first, or suppress duplicate stop/cancel requests in the caller/UI.
Key:BODYCAM_RECORDING_FAILEDMeaning: The bodycam recording pipeline failed before the clip could be finalized successfully.Potential Fix: Review the support ref, then verify the bodycam stream, recorder pipeline, duration/size limits, and upload handoff path.
Key:BODYCAM_NOT_WORNMeaning: The player attempted to enable bodycam without matching the configured clothing/bodycam requirements.Potential Fix: Equip the required bodycam clothing/components or relax the configured clothing validation.
Key:BODYCAM_WATCH_ACTIVEMeaning: Bodycam disable was blocked because the bodycam is currently being watched.Potential Fix: Stop the remote watch session first, or use an authorized force-off flow if policy allows it.
Key:BODYCAM_SOUND_LEVEL_INVALIDMeaning: The requested bodycam sound level was not a valid number within the accepted range.Potential Fix: Pass a numeric value greater than0and less than or equal to1.
Key:BODYCAM_UPLOAD_FAILEDMeaning: The finalized bodycam clip failed to upload to CAD.Potential Fix: Check API connectivity, auth, upload endpoint availability, and the support ref for the upload failure context.
Key:CADDISPLAY_F8_PERMISSIONMeaning: CAD display keybind commands are blocked by ACE permissions.Potential Fix: Grant the listed CAD display command permissions to players who should be able to use them.
Key:CALL_MISSING_DETAILSMeaning: A call-related command was used without the required details.Potential Fix: Re-run the command with the required message, description, or argument payload.
Key:CALL_SEND_FAILEDMeaning: A call could not be sent to CAD.Potential Fix: Check the support ref, then verify CAD API availability, call payload validity, and that API sending is enabled.
Key:CALL_TEMPLATE_INVALIDMeaning: The configured call template file is missing or invalid.Potential Fix: Verify the template file exists, is valid JSON, and matches the configured filename/path.
Key:PANIC_F8_PERMISSIONMeaning: The panic keybind command is blocked by ACE permissions.Potential Fix: Allowcommand.panicfor the intended players in ACE permissions.
Key:VEHREG_NO_CHARACTERMeaning: No active CAD character was found for the vehicle registration action.Potential Fix: Log into a CAD character first, then retry the registration action.
Key:VEHREG_CREATE_FAILEDMeaning: The vehicle registration record could not be created in CAD.Potential Fix: Check record template/config values, payload data, and CAD API availability.
Key:VEHREG_PLATE_TAKENMeaning: The requested plate is already registered in CAD.Potential Fix: Choose a different plate or locate and update the existing CAD registration record.
Key:UNITSTATUS_INVALID_STATUSMeaning: The requested unit status does not exist in configuration or is outside the supported range.Potential Fix: Use a configured status name/number and verifyunitstatusstatus mappings in its config file.
Key:APIWS_DEPENDENCY_MISSINGMeaning: The SignalR dependency required for API WebSocket connectivity is missing.Potential Fix: Install the missing package in thesonorancadresource, typically@microsoft/signalr, and restart the resource.
Key:APIWS_AUTH_FAILEDMeaning: The API WebSocket hub rejected authentication.Potential Fix: VerifycommunityID,apiKey, andserverId, then confirm the key is valid for the target community.
Key:APIWS_CONFIG_MISSINGMeaning: The API WebSocket connection could not start because required config values were missing.Potential Fix: EnsurecommunityID,apiKey, andserverIdare all present and loaded before WebSocket startup.
Key:APIWS_CONNECTION_FAILEDMeaning: The API WebSocket transport could not establish a connection.Potential Fix: Check outbound HTTPS/WebSocket connectivity, API URL correctness, and firewall/proxy rules.
Key:APIWS_RECONNECT_FAILEDMeaning: Reconnect attempts to the API WebSocket hub are repeatedly failing.Potential Fix: Treat this like a persistent connectivity or auth problem; review the first connection failure and fix that root cause.
Key:APIWS_PUSH_EVENT_FAILEDMeaning: A push event delivered over the WebSocket connection could not be decoded or processed.Potential Fix: Validate the incoming event payload shape and inspect the support ref for the handler that failed.
Key:APIWS_SEND_FAILEDMeaning: A message could not be sent over the API WebSocket connection.Potential Fix: Confirm the WS connection is active and authenticated before sending unit/call updates.
Key:PLUGIN_VERSION_FILE_LOAD_FAILEDMeaning: The local plugin version file could not be loaded from disk.Potential Fix: Confirmsonorancad/version.jsonexists and is readable.
Key:PLUGIN_VERSION_FILE_PARSE_FAILEDMeaning: The local plugin version file exists but could not be parsed.Potential Fix: Repair malformed JSON inversion.jsonor replace it from a clean release.
Key:PLUGIN_UPDATER_RESPONSE_INVALIDMeaning: The remote updater responded with invalid or unusable data.Potential Fix: Retry later and verify outbound network access to GitHub/raw content endpoints.
Key:PLUGIN_NOT_FOUNDMeaning: A requested plugin or submodule could not be found locally.Potential Fix: Verify the plugin name, installation path, and that its config/resource files exist.
Key:PLUGIN_MANIFEST_ENTRY_MISSINGMeaning: A local submodule was not present in the remote updater manifest.Potential Fix: If it is a custom submodule, this may be expected; otherwise update to an official supported submodule build.
Key:PLUGIN_MANIFEST_VERSION_MISSINGMeaning: A remote updater manifest entry was missing a version field.Potential Fix: Replace the manifest source with a valid upstream release or retry after the remote manifest is corrected.
Key:PLUGIN_CONFIG_VERSION_MISSINGMeaning: A plugin config did not declare its current config version.Potential Fix: Update the plugin config from the latest*_config.dist.luaand ensure the version field is present.
Key:PLUGIN_CONFIG_BACKUP_FAILEDMeaning: The plugin updater could not create a config backup before modifying files.Potential Fix: Check write permissions for the SonoranCAD configuration directory and available disk space.
Key:PLUGIN_CONFIG_PARSE_FAILEDMeaning: A plugin or submodule configuration file could not be parsed, compiled, or executed safely.Potential Fix: Repair the matching*_config.luafile so it defines a validlocal config = {}table and contains no Lua syntax/runtime errors.
Key:CIV_NO_CHARACTERS_FOUNDMeaning: No CAD character records were found for the player.Potential Fix: Ensure the player is linked and has at least one valid CAD character, or enable custom IDs if you want a fallback.
Key:CIV_CUSTOM_IDS_DISABLEDMeaning: The server has disabled custom civilian IDs.Potential Fix: EnableallowCustomIdsin the civ integration config if that workflow should be allowed.
Key:CIV_REFRESH_DISABLEDMeaning: Manual character cache refresh is disabled.Potential Fix: Enable the purge/refresh option in config if players should be allowed to force-refresh ID data.
Key:CIV_UNKNOWN_SUBCOMMANDMeaning: An invalid civilian ID command subcommand was used.Potential Fix: Use/id helpand re-run the command with a supported subcommand.
Key:CIV_NO_NEARBY_PLAYERSMeaning: The player attempted to show an ID but no nearby viewers were found.Potential Fix: Move closer to another player and retry theshowaction.
Key:CALL_CREATE_FAILEDMeaning: A dispatch call create operation failed before returning a valid call ID.Potential Fix: Inspect the payload fields sent to CAD and verify API availability and permissions.
Key:CALL_UNEXPECTED_RESPONSEMeaning: CAD returned a success path without the expected data, such as a missing call ID.Potential Fix: Review the API response body and confirm the integration and API versions are compatible.
Key:DISPATCH_CALL_NOT_FOUNDMeaning: A dispatch action referenced a call that was not present in cache.Potential Fix: Verify the call ID is current and that call cache synchronization is working before retrying the action.
Key:ERS_MAPPING_FAILEDMeaning: ERS field mapping logic failed while converting ERS data into CAD payload fields.Potential Fix: Review custom mapping functions and field names in the ERS integration config for nil values or bad return types.
Key:ERS_PAYLOAD_MALFORMEDMeaning: An ERS event payload was missing required top-level fields or had an invalid structure.Potential Fix: Validate the ERS event payload contract and adjust any custom hooks that modify it.
Key:ERS_COORDS_MISSINGMeaning: An ERS event did not provide usable coordinates for the CAD action.Potential Fix: Ensure the originating ERS event includes proper coordinates and that any transform step preserves them.
Key:ERS_CALL_ID_INVALIDMeaning: ERS attempted to update or attach to a call using an invalid stored call ID.Potential Fix: Check the local saved-call cache and ensure the create-call step succeeded before later actions reference it.
Key:ERS_RESOURCE_NOT_STARTEDMeaning: The Night ERS resource required by the integration is not started.Potential Fix: Start the ERS resource before enabling the ERS integration submodule.
Key:FRAMEWORK_RESOURCE_MISSINGMeaning: A required framework resource likeqb-coreores_extendedis not running.Potential Fix: Start the configured framework resource and verify the integration is targeting the correct framework.
Key:FRAMEWORK_IDENTITY_MISSINGMeaning: Framework identity or player data could not be retrieved.Potential Fix: Check that the player is fully loaded into the framework and that the expected identity export/event is available.
Key:FRAMEWORK_QUERY_INVALIDMeaning: A framework SQL query or parameter set was invalid and was rejected before execution.Potential Fix: Ensure the query is a non-empty string and the parameters are passed as a key/value table rather than an array.
Key:LOCATIONS_CONFIG_MISSINGMeaning: The locations/livemap vehicle model config file could not be found.Potential Fix: Restore the missing config file or update the configured path to a valid file.
Key:LOCATIONS_CONFIG_INVALIDMeaning: The locations/livemap config file exists but could not be decoded.Potential Fix: Repair malformed JSON in the vehicle model configuration file.
Key:LOCATIONS_CLIENT_ERRORMeaning: A client reported an error while sending location data.Potential Fix: Check client logs for the specific failure and verify required dependencies like postals and location hooks are configured.
Key:POSTALS_RESOURCE_UNAVAILABLEMeaning: A client-side feature requested postal data, but the configured postal source was unavailable.Potential Fix: Start the configured postal resource or switch to a valid postal mode/source in config.
Key:POSTALS_FILE_INVALIDMeaning: The configured client-side postal file was missing or invalid.Potential Fix: Restore the referenced postal file, validate its JSON, and confirm the configured filename is correct.
Key:RECORDPRINTER_UNIT_MISSINGMeaning: Record printer could not resolve the player to an active CAD unit.Potential Fix: Ensure the player is logged into CAD and present in the unit cache before printing.
Key:RECORDPRINTER_DIRECTORY_FAILEDMeaning: Record printer could not create or resolve its output directory.Potential Fix: Check write permissions and folder creation behavior for the record printer output path.
Key:RECORDPRINTER_SAVE_FAILEDMeaning: Record printer failed to save the generated PDF.Potential Fix: Verify write permissions, disk space, and that the generated PDF data is valid.
Key:RECORDPRINTER_SHARE_INVALIDMeaning: Record printer rejected a share request because the URL or target list was invalid.Potential Fix: Validate the shared URL and ensure at least one valid target player or identifier is supplied.
Key:SONRAD_CALLCOMMANDS_MISSINGMeaning: Sonrad attempted an action that depends on thecallcommandssubmodule.Potential Fix: Enable/start thecallcommandssubmodule before using Sonrad panic/call features.
Key:SONRAD_CONFIG_MISSINGMeaning: Critical Sonrad configuration values are missing.Potential Fix: Updatesonrad_config.luafrom the latest template and fill in the missing required values.
Key:CADDISPLAY_FRAMEWORK_UNAVAILABLEMeaning: CAD display could not access the configured framework export.Potential Fix: Confirm the selected framework resource is started and that its export name matches the integration config.
Key:CADDISPLAY_PLACEMENT_INVALIDMeaning: CAD display placement data could not be loaded or parsed.Potential Fix: Repair the placement file JSON/Lua data or delete bad saved placement data so defaults can be rebuilt.
Key:CADDISPLAY_VEHICLE_UNIDENTIFIEDMeaning: CAD display could not determine what vehicle the player was targeting.Potential Fix: Retry while targeting a valid supported vehicle and verify the display interaction logic has correct entity context.
Key:KICK_QUEUE_UNAVAILABLEMeaning: The kick module could not queue a CAD logout/kick for the player.Potential Fix: Ensure the player is linked and currently represented by an active unit before the kick action runs.
Key:INVALID_API_MODEMeaning: The configured SonoranCAD API mode was invalid, so the resource fell back to production mode.Potential Fix: Setmodeto a supported value such asproductionordevelopment.
Key:DEPRECATED_DEBUGPRINTMeaning: Deprecated logging helperdebugPrintwas used somewhere in the runtime path.Potential Fix: ReplacedebugPrint(...)calls withdebugLog(...)in custom integrations or older submodule code.
Key:JSON_DECODE_FAILEDMeaning: SonoranCAD failed to decode a JSON string and continued with a default or empty value.Potential Fix: Validate the JSON source that triggered the warning and correct malformed payload or file contents.
Key:JSON_ENCODE_FAILEDMeaning: SonoranCAD failed to encode a Lua value into JSON and continued with a fallback value.Potential Fix: Check the table being encoded for unsupported values such as functions, userdata, or recursive structures.
Key:APIKEY_CONVAR_UNINITIALIZEDMeaning: SonoranCAD started before the bundled convar setup fromsonorancad.cfginitialized the API key path.Potential Fix: Useexec sonorancad.cfgand make sure it runs beforeensure sonorancad.
Key:OLD_FXSERVER_VERSIONMeaning: The running FXServer build is older than the version this SonoranCAD release was tested against.Potential Fix: Update FXServer to the tested version or newer before troubleshooting feature regressions.
Key:PLAYER_IDENTIFIER_MISSINGMeaning: A player connected without the configured primary identifier, so some CAD features may not work for that player.Potential Fix: Ensure the configured identifier type is actually available on your server and that the player is connecting through the expected identity provider.
Key:PLAYER_LINK_REQUIREDMeaning: A player attempted a CAD-linked workflow without having a linked CAD account.Potential Fix: Have the player run the configured link command, complete the link flow, and retry after the CAD link exists.
Key:LEGACY_HTTP_PUSH_EVENTMeaning: SonoranCAD received a legacy HTTP push event on/eventwhile WebSocket push delivery is preferred.Potential Fix: Review your CAD/server push-event configuration and move the server onto the API WebSocket push path where available.
Key:UNHANDLED_WARNINGMeaning: A warning was logged without a more specific registered warning code, so it was normalized into the generic warning bucket.Potential Fix: Use the support ref and warning text in logs to identify the exact caller, then register a dedicated warning code if the condition needs clearer support guidance.