Source: https://docs.amadalis.ai/trust/known-limitations/ # Known limitations and unsupported features Check this page for what is not supported yet, what has limits and which guide explains the supported route. Review the relevant limits before relying on a workflow or approving a change in the site admin or account. Checked against the product’s code on 7 November 2026. This page was checked against the product’s code. That check does not confirm that a particular hosted site is running every change. Ask support to confirm any capability your project depends on. ## Access and integrations - **Support access:** a grant controls when support can start a read only visit. Revoking the grant stops new entries and ends its open support session on the next request after the grant check refreshes, within 30 seconds. At expiry, the next request ends the session. If the grant cannot be checked, the request is blocked while the session is kept. Read [Support access](https://docs.amadalis.ai/account/security/#support-access) for the separate entry paths and current limits on grants and records for other sites. - **External agents:** EmDash’s Model Context Protocol (MCP) interface for outside agents is disabled on Praxis sites. Personal tokens cannot make changes through EmDash’s software interface (API). The public machine files describe readable content; they do not provide a running MCP service. Reads with a personal API token must also pass the team’s [API token checks](https://docs.amadalis.ai/account/site-access-and-settings/#personal-api-tokens). - **[Single sign-on (SSO)](https://docs.amadalis.ai/reference/glossary/#single-sign-on-sso):** the connection supports the OpenID Connect sign in standard. It requires an email domain registered and verified on your account. The refusal directs you to support for that step. The alternative SAML sign in standard is not supported by this connection. - **Session policy:** If the account cannot read the policy, it pauses access if the last known policy has a rule or its history cannot be read. A team with no recorded policy or no last known rules can continue. The page says “We could not check your team’s sign-in rules; try again in a minute.” It keeps the sign-in session for a retry. The policy is checked on your Praxis account and inside open site admin sessions. If the site cannot read the policy, it uses a policy read within the last five minutes. Without one, it pauses access if the last known policy has a rule or that record cannot be read. A team with no recorded policy or no last known rules can continue. A server that last read a rule may still pause access after another server has read that the rules were cleared. The paused page asks you to try again in a minute. An existing session is kept; a refused new site sign in opens no session. - **Staging:** the normal signup flow provisions one production environment. It does not create a separate staging copy. - **Restore:** restoring a whole site is an action for Amadalis staff. It is not a customer action on the Sites tab. Taking or downloading a content backup from EmDash’s **Backup settings** screen is not available on the hosted site’s database yet. - **Data location:** the database region shown in your account does not pin the network, caches or AI processing to that region. ## Editing and undo - **Undo:** not every change can be reversed. Read each approval card before confirming. Visitor erasure is permanent. - **Theme Studio:** saving or deleting a theme does not offer the same undo flow as activating a theme. - **Page type themes:** a page type’s default theme is a reserved setting. The public render does not use it yet. - **Languages:** the host is configured for English and Spanish. Discuss any other language requirement before a migration. ## Forms and commerce - **Forms:** there is no file upload field in the native form field list. A migrated form with an unsupported field or behavior needs review. - **Imported products:** products brought in by a WordPress import are read only in **Products**. The screen says: “This product was brought in by your import, so it cannot be changed here yet.” - **New product prices:** the Products screen takes prices in US dollars. Confirm currency requirements before setting up a store. ## Audiences and measurement - **Rule audience counts:** “not counted yet” is not a count of zero. Rules are checked as visitors arrive, and the product does not keep a running count for every rule. - **Affinity setup:** [affinity](https://docs.amadalis.ai/reference/glossary/#affinity) needs saved tuning, active content for an affinity audience and a connected personalization service. Confirm setup with Amadalis before relying on recommendations based on interests. - **Event definitions:** an event can be listed before anything on the site sends it. It collects nothing until something does. - **Experiment results:** the scheduled saved result is calculated nightly for each running experiment with a locked plan. Do not expect that saved result to update with every visitor. ## Migration Imported pages and posts start as drafts, but an import can activate redirects, replace a menu with the same name and make its theme live. Scope the destination and timing with Amadalis. See [Migration as a service](https://docs.amadalis.ai/agencies/migration-as-a-service/) for the review workflow. ## Records and erasure Visitor events are kept with no limit until you set a [retention period](https://docs.amadalis.ai/reference/glossary/#retention). Once you set one, events older than it are deleted on the site’s regular scheduled run, but only after an archive export has covered them. An approved change goes ahead even if its Activity record fails to save; the failure is logged on the server. The change keeps any Undo it offered on its receipt. Visitor erasure can finish in the site’s database while reset of live state or export cleanup still needs attention. Read the receipt. Orders and payments are retained without their visitor reference, and an order keeps the customer name and email recorded at checkout. Visitor erasure does not remove form submissions; erase those separately. Files already downloaded cannot be recalled. See [Privacy and consent](https://docs.amadalis.ai/trust/privacy-and-consent/) for the consent rules and erasure scope.