Capabilities and troubleshooting
Use feature states to understand which store operations are available. This guide also covers common import and preview errors.
Feature states
- Enabled: the store, subscription and account permit the operation.
- Needs setup: complete the required configuration before using the feature.
- Not included: the current subscription does not include the feature.
- Unsupported: the runtime or store cannot provide the required operation.
Feature cards do not grant permissions. Access is checked by the server. Sample cards and mock-mode values may illustrate these states without providing the corresponding operation.
Import errors
Invalid source bundle: select the .banow-source.json file created by banow-template bundle. Do not select a built artifact, npm package or compressed archive.
File too large: reduce source or image sizes and generate a new bundle. See upload limits.
Fingerprint mismatch: export the current source again with bundle, then select the new file. Do not edit the expected fingerprint manually.
Import interrupted: refresh Projects to check whether the project was saved. Retry with the same selected file and name where possible. If either changes, select the file again to start a new import attempt.
Build and preview errors
Build failed: fix the reported source error and choose Save & build, or restore an available checkpoint. The visible preview may be the last successful build until the next build succeeds.
Build service unavailable: contact your workspace administrator to check the backend, validator and isolated worker configuration.
Preview connection failed: check that the required applications are running and use the configured addresses. In local development, the public app normally runs on port 3010 and the merchant storefront/validator on port 3000. The preview connection accepts only configured origins.
Account access
If Studio asks you to sign in, use the account that owns the project. Private releases are not automatically shared with another account or business. If you cannot save a release, finish the source build first and resolve any unsaved changes.
Historical data
Store records are separate from template presentation. Hiding a feature or changing a design does not grant or remove permissions to historical records. Access to past orders and customer data follows the store's account permissions.
