Troubleshooting

Check the following:

1. Is the code actually running in a browser environment?
2. Does the selector passed point to an existing object?
3. Is a configuration object actually being passed?
4. Is at least embedId or formDefinition set?

Check the following:

1. Is embedId correct?
2. Is the form published?
3. Is srcUrl set correctly?
4. Is your domain stored in Formcentric?
5. Do dataUrl, formappUrl or designUrl point to the right endpoints?
6. If you are using local themes, have theme and template resources been configured correctly?

Check the following:

1. Is the theme CSS being loaded?
2. Are the theme templates loaded?
3. Are skipThemeLoad and skipTemplatesLoad set only if you are actually bundling these assets yourself?
4. Are themeDir and theme or the explicit asset URLs fully configured?

The SDK is restart-based. Many configuration values take effect only on initialisation.

Check the following:

1. Is there an explicit re-mount after relevant configuration changes?
2. Are you expecting init-time fields to be carried across live to a running instance?
3. Is embedId staying stable if handovers between instances are required?

If the same embedId is mounted multiple times, the SDK will force stricter conflict behaviour than the legacy path.

Check the following:

1. Is the same embedId already active on another element?
2. Should conflictBehavior be set to 'stop-existing' for your use case?
3. Are stop() or unmount() being correctly awaited before a re-mount?