Error Dictionary

This reference explains and provides solutions for common error messages encountered in Momen during editing, deployment, and runtime. For step-by-step debugging workflows, see the Troubleshooting Guide.

Combine error messages with your business context. Permission, configuration, and data uniqueness issues are the most common root causes.

Deployment and Runtime Errors

Error Message	Explanation	Cause	Solution
Permission check failed	User lacks permission for the action	Insufficient permission settings	Adjust permission settings
Duplicate key value violates unique constraint	Attempted to insert a duplicate value in a unique field	Data constraint violation	Check and modify duplicate values
Delete or update must have a filter	No filter condition was provided for delete/update operations	Missing filter condition	Ensure a filter condition is set correctly
Table access denied	User lacks access permission for a table	Permission settings issue	Adjust table access permissions
Actionflow not found	Backend deployment was not completed	Actionflow missing from backend	Deploy the Actionflow and retry
Another app is deploying	Concurrent deployments detected	Backend is already in deployment	Wait for the current deployment to finish
CANNOT_DEPLOY_AN_OLDER_SCHEMA	Deployment failed	The project is not using the latest schema version	Refresh the page and retry
PROJECT_ENV_CONFIG_SYNC_ERROR	Data synchronization failure	Synchronization failed during backend deployment (e.g., data model, Actionflow)	Refresh the page and retry
TARGET_PLATFORM_IS_DEPLOYING	Project deployment in progress	The same build target is currently being deployed	Wait for deployment to finish and retry
SUPPORT_SERVICE_IS_DEPLOYING	Backend deployment in progress	A new deployment request was issued during an ongoing backend deployment	Wait for the deployment to complete before retrying
TABLE_NAME_TOO_LONG	Table name exceeds length limit	The table name exceeds 62 characters	Shorten the table name
TABLE_NAME_ALREADY_EXISTS	Duplicate table name	The table name already exists	Rename the table
Validation error of type Wrong Type	Parameter type validation error	Bound value type does not match the expected field type	Re-bind data with the correct type

Common Editing Validation Errors

When the editor error icon shows a count, click it to jump to the issue. Frequent patterns include:

Error Pattern	Cause	Solution
Type mismatch	Field expects one type (e.g., `Int`) but receives another (e.g., `String`)	Correct the bound value or input
Missing required field	A required property, parameter, or binding is empty	Fill in or bind the required field
Unknown table or field	Referenced table/field was deleted or renamed	Re-select a valid table/field or remove the reference
Actionflow not found (editor)	Actionflow reference is broken	Recreate or re-link the Actionflow
Circular dependency in components	Components depend on each other in a loop	Break the dependency chain

Permission Error Response Example

When a user lacks table access, the GraphQL response typically looks like:


{
  "data": null,
  "errors": [
    {
      "errorCode": 403,
      "extensions": { "classification": "TABLE_ACCESS" },
      "message": "User 1 has no permission for SELECT on order"
    }
  ]
}

Steps to resolve:

Confirm the user has the correct role assigned.
Verify the role’s data and action permissions in Permissions.
Sync changes if permission changes have not been deployed.