This page covers common issues you may encounter when building or publishing a configurator in TwikBot, along with suggested solutions. If you cannot resolve an issue using this guide, contact support.twikit.com.
General Debugging
Check the browser console first. Most issues with a configurator loading or behaving unexpectedly will produce an error or warning in the browser's developer console. Open it via F12 (or right-click → Inspect → Console) and look for errors when the issue occurs.
Set the log level in the Graph Editor for more detail. TwikBot allows you to configure the log level directly in the Graph Editor. Increasing the log level will surface more detailed information in the browser console, making it easier to identify the source of a problem during development and testing.
Login & Account Issues
Cannot log in. Verify that you are using the correct credentials provided by Twikit. If you have forgotten your password, contact support.twikit.com — self-service password reset is not currently available.
MFA setup is not working. Make sure your authenticator app's time is synchronised correctly — MFA codes are time-based and will fail if your device clock is out of sync. If the issue persists, contact support to reset your MFA configuration.
Wrong organisation is active. If you manage multiple organisations, check the active organisation in the account section at the bottom of the navigation menu before making any changes. Changes made in the wrong organisation context cannot be automatically undone.
Resource Upload Issues
Upload fails or times out. Check that your file meets the supported file type and size requirements listed in Resources | Supported file types. Very large files may time out — optimise the asset and try again.
Geometry looks incorrect after upload. This is usually caused by issues in the source file — non-manifold geometry, flipped normals, or incorrect scale. Return to Blender, fix the geometry following the steps in [Tutorials → Preparing Resources in Blender], and re-upload.
Textures appear black or missing. Verify that the texture file format is supported and that the UV map on the mesh is correctly set up. If the texture requires a specific UV channel, confirm that the correct channel is referenced in the material setup.
Graph Editor Issues
Disconnected nodes cause the configurator to fail loading. All required input connections on a node must be connected for the graph to function correctly. A disconnected required input can prevent the entire configurator from loading. Check all nodes for missing connections — disconnected inputs are typically highlighted in the Graph Editor. Check the browser console for specific error messages pointing to the affected node.
Graph becomes slow or unresponsive. Very large or complex graphs can become slow to work with. Use post-its to organise sections, collapse node groups where possible, and avoid unnecessary duplicate nodes. If performance is severely degraded, contact support.
Duplicate external parameter IDs cause the configurator to crash. Every external parameter in the Graph Editor must have a unique ID. If two or more external parameters share the same ID, the configurator will fail to load. Review all external parameters and ensure each one has a distinct identifier before releasing or testing.
Changes in the Graph Editor are not reflected in the preview. Make sure you have saved your changes. Unsaved changes are not applied to the preview. If the issue persists after saving, try refreshing the preview.
Visualisation & Rendering Issues
Mesh appears with incorrect shading or dark patches. This is typically caused by inverted normals. Check and correct normals in Blender before re-uploading the asset. Adding sharp edges where needed can also resolve incorrect shading at hard edges.
Materials appear flat or incorrect. Verify that materials are correctly connected to the 3D output node in the Graph Editor. Check that the correct material slots are being targeted if the mesh has multiple materials.
HDRI or lighting is not visible. Confirm that the scene node is correctly set up and that the HDRI resource has been uploaded and connected. Check that the environment map intensity is not set to zero.
Shadows are missing or incorrect. If using a baked shadow plane, verify that it is correctly positioned beneath the product and that the shadow map texture is properly connected. For real-time shadows, check the light node settings in the Graph Editor.
Performance Issues
Configurator loads slowly. The most common causes are high polygon counts, large uncompressed textures, or too many simultaneously loaded assets. Use the MB tool in the Graph Editor to check the memory footprint and identify the largest contributors. Optimise assets following the guidelines in [Best Practices → Performance Optimisation].
Configurator crashes or reloads on mobile, particularly iOS. iOS devices have strict memory limits. If the configurator exceeds available memory the browser tab will crash and reload. Use the MB tool in the Graph Editor to monitor memory usage and reduce it by compressing textures, lowering polygon counts, and limiting simultaneously loaded geometry. See [Best Practices → Performance Optimisation] for detailed guidance.
Configuration changes are slow to update. Slow parameter updates are usually caused by heavy geometry swaps or complex material recalculations. Where possible, use visibility logic instead of full geometry swaps, and simplify material graphs.
Export File Issues
Export files are not generated after an order is placed. Verify that output nodes are correctly configured in the Graph Editor and that the product has been released after the output nodes were added or changed. Export files are only generated based on the logic in the released version of the product.
Export file content is incorrect or missing elements. Check the output node configuration in the Graph Editor. Verify that all required parameters are connected and that the correct modifiers are applied. Place a new test order after making corrections and inspect the resulting file.
Export file does not meet manufacturing specifications. Review the file against the manufacturer's requirements. Common issues include incorrect units, missing line thicknesses, or incorrect corner radii. Adjust the relevant output modifiers in the Graph Editor and re-test.
Project Publishing Issues
Publish button is not available. A project must have at least one enabled product with a valid release version before it can be published. Check that your product has been released and is enabled in the project setup.
Changes to a product are not reflected on the live configurator after publishing. Verify that a new product release was created after the changes were made, and that the project is referencing the new release version. Publishing a project without updating the release version will not pick up new changes.
Standalone configurator website is not accessible. Check that the project has been published and that password protection is not enabled unintentionally. If the issue persists, verify the project URL and contact support.
Web SDK Integration Issues
Configurator does not load in the embedded page. Check that the plugin script URL is correctly included in the page and that the productKey matches the product ID in TwikBot. Verify there are no JavaScript errors in the browser console that might be blocking initialisation.
createContext() callback is not firing. Ensure the plugin script is loaded and executed before the initialisation script. The plugin script must appear above the initialisation script in the HTML. Check the browser console for errors.
Parameters are not appearing. Verify that the parametersReady callback is correctly implemented and that the container element exists in the DOM at the time the callback fires. See Web SDK Reference | Create context for the correct implementation.
If your issue is not covered here, contact our support team at support.twikit.com with a description of the issue, the browser console output, and the product or project ID where the issue occurs.