Known Issues
Dynamic Runtime Challenges
Gateway supports procedural (runtime-authored) challenges via the RegisterProceduralChallenge API.
Unlike static challenges, procedural challenges are constructed and injected at runtime rather than defined
upfront in a Data Asset — making daily, weekly, event-driven, and procedurally generated challenge sets possible
without any design-time authoring.
There are a couple limitations to be aware of when using procedural challenges:
- Extension state is not persisted for procedural challenges. If a challenge has an extension that carries runtime state, that state will not survive a session boundary. Stateful behavior should use Gateway's stat system instead.
- Gateway provides no scheduling or rotation primitives. RegisterProceduralChallenge and UnregisterProceduralChallengesInGroup are the building blocks, but when and how procedural challenges rotate (if at all) is left entirely to the project.
Reporting Issues
If you encounter a bug or limitation not listed here, please reach out so it can be tracked and addressed.
Known issues will be documented on this page as they are identified, along with workarounds where available.