--- title: "No EFG Cryptography Key Provided" slug: "platform-configuration-no-efg-cryptography-key-provided" updated: 2026-08-14T07:50:21Z published: 2026-08-14T07:50:21Z canonical: "help.csgi.com/platform-configuration-no-efg-cryptography-key-provided" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.csgi.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # No EFG Cryptography Key Provided ## KW-01-000-00-0002 Platform configuration: No EFG Cryptography Key Provided in Configuration and Startup. ### What This Error Means Internal platform issue in Platform configuration: No EFG Cryptography Key Provided. Graph configuration cannot fix this; escalate to Xponent JO Operations. ### Recommended Action 1. Open a ticket with Xponent JO Operations. Include project, environment, graph or deployment, transaction ID, timestamp, and the full KW message. ### Detailed Guidance > [!NOTE] > Full Engine Message > > - KW-01-000-00-0002 Platform configuration: No EFG Cryptography Key Provided > [!NOTE] > Trigger Conditions > > - Emitted by an Operations-managed Xponent JO platform service or dependency. > [!NOTE] > Escalation Threshold > > - Escalate to Xponent JO Operations this error is platform-owned or references managed infrastructure. > [!NOTE] > Related Metrics / Dashboards / Alerts > > - Platform service/dependency health and graph failure rate for the same time window. ### Article Context > [!NOTE] > Arbiter Service: Platform configuration > > Xponent JO Operations: No EFG Cryptography Key Provided > [!NOTE] > Graph Execution Engine: Platform configuration > > Xponent JO Operations: No EFG Cryptography Key Provided