Troubleshooting

Each entry below lists the symptom (the message shown in the interface), the cause and the fix. If an error is not listed, send the run ID from Run history to a project editor or admin.

Publishing an action

When publishing fails, the interface shows Publish refused: followed by the list of problems returned by the server.

Message	Cause	Fix
SQL dùng {{x}} nhưng chưa khai báo param này (the SQL uses {{x}} but this param is not declared)	The SQL contains {{x}} but the Params section has no param x.	Click Add N params from the SQL or Add a param with the exact name, then publish again.
param "x" không được dùng trong SQL (param x is not used in the SQL)	A param is declared but the statement does not use it.	Remove the param or use it in the SQL.
{{x}} nằm ở vị trí identifier (tên cột/bảng) nên phải khai báo type: enum kèm values (identifier position needs an enum with values)	A param sits where a column or table name goes (for example ORDER BY {{x}}) but is not an enum with a fixed list.	Change the param type to enum and fill in Enum values. An enum whose list comes from another action cannot be used here. See Parameters.
action kind=read nhưng SQL có UPDATE (or INSERT, DELETE): a read action contains a write	A Read-only action contains a write statement.	The mode cannot be changed after publishing. Create a new action in Writes data mode.
SQL có N câu lệnh … (the SQL has N statements)	The action contains several statements. On MySQL, each action can contain exactly one statement.	Split it into several actions, or use a JS action to call them in turn.
SQL chứa DDL (…); data source này không bật allowDDL (schema-changing statement not allowed)	The SQL contains DROP, ALTER, TRUNCATE, GRANT…	Remove schema-changing statements from the action.
không parse được SQL, cần review thủ công: … (the SQL could not be parsed)	The server could not analyze the statement, so it cannot check it for safety.	Rewrite the statement using standard syntax.

Note

Publish error messages are generated by the server and are shown in Vietnamese in both interface languages. The English text in parentheses explains each message.

Running actions

Symptom	Cause	Fix
No Add to the queue or Bulk run option	These two ways of running are only available for SQL actions in Writes data mode.	Read-only actions and JS actions run directly with Run.
No Try a run button on the action page	The action has never been published. Drafts cannot run.	Click Publish. Try a run appears after publishing.
The run page says This action is not published	Same as above.	Publish the action on the Action page before running it.
You edited the action but runs still show the old result	The Run action page always runs the published version, never the draft.	Save the draft and publish a new version.
The action is missing from the list when prod is selected, or the message “This action isn’t applied in this environment.” appears	New actions apply only to non-production environments.	An editor enables prod in the action’s Applies to environments card (with a confirmation step).
“This action’s data source has no connection in this environment.”	No data source connection has been saved for the selected environment (common after switching to prod).	An admin switches to that environment and saves the connection in the Config per environment card.
“You haven’t been given access to run this action”, or the action is missing from your list	The action is restricted and you have not been granted access. This also applies to owners and admins.	Ask an admin to grant access on the action’s Settings & access tab. See Access control.
“Your IP is not on the allowlist.”	The environment has an IP allowlist and your current IP is not on it.	Use an allowed network or VPN, or ask an admin to add your IP on the Environments page.
“Too many requests. Try again shortly.”	You exceeded the run rate limit.	Wait a moment, then run again. For a write action that needs to run many times, use Bulk run. See Limits.
“Showing only the first N rows — narrow the filters to see everything”	The result exceeds the action’s Max rows.	Add filters, or ask an editor to raise the maximum row count.
Timed out error	The statement ran longer than the action’s timeout, or waited more than 3 seconds for a lock.	Narrow the query or add an index. Write actions can run in the background with Add to the queue.
Write in a read-only action error	The statement attempted a write inside a read-only transaction.	Use a Writes data action for writes.
A picker says “You don’t have access to this list — contact a project admin.”	The param takes its list from a source action you are not allowed to run.	Ask an admin to grant you run access on the source action.
A picker says “This list isn’t available in the selected environment.”	The source action is not applied in this environment, or its data source has no connection here.	Enable the environment for the source action and save the connection.

Screens (views)

Symptom	Cause	Fix
The screen shows but part of it is empty, with “Part of this screen will have no data because you haven’t been given access.”	Screens run with the viewer’s permissions; publishing a view grants no permissions. An action that the screen calls was denied (403).	An admin grants you access on each action the screen uses.
A view is missing from Screens	The view is not published, or not enabled for the selected environment.	An editor publishes the view and enables the environment in the view’s Applies to environments card, or you switch to an environment where it is enabled.
“This screen isn’t applied in prod” when opening a link	Same as above, for the selected environment.	Switch environment in the top bar, or ask an editor to enable the screen for this environment.
“The view is not responding — it may be stuck in a loop.”	The view’s code keeps running without returning.	Click Reload, then ask an editor to fix the view code.

Data source connections

Symptom	Cause	Fix
Could not connect to the data source	The execution server cannot reach the host: wrong host/port, or the firewall is not open to the deployment’s egress IP.	Check the host and port; open the firewall to the egress IP. See Deployment.
Data source rejected login	Wrong user or password.	Re-enter User and Password, then click Test the config as typed.
Certificate error with On, verify the certificate	The database uses its own CA (RDS, Cloud SQL, an internal CA).	Load the CA into CA (PEM) with Choose file or Paste PEM.
Certificate name mismatch	The host is an IP address, or a name different from the one in the certificate.	Fill in Server name in the certificate. On MySQL, the host must be a name listed in the certificate.
The server requires a client certificate	The database is configured for mTLS.	Load Client certificate (PEM) and Private key (PEM) without a passphrase.
Test the config as typed fails even though the saved config is right	This button does not use the saved password and PEM files.	Re-enter the password and PEM, or save and click Test the saved config.
“File too large — 200 KB max.”	The PEM file exceeds the limit.	Load only the certificates you need.
An editor cannot see the prod connection	The editor’s role in prod is capped at viewer.	An admin raises their Maximum role to editor for that environment, if appropriate.

Variables and secrets

Symptom	Cause	Fix
You cannot see a secret’s value	Secrets are write-only and nobody can read them back, including admins and owners. This behavior is by design.	To change the value, click Change value and overwrite it. Get the original value from its issuer (the API provider, your password manager…).
Saving a variable warns that it “looks like a secret”	The key or value looks like a token or password. Variable values are visible to every editor and stay in the audit log.	Click Save as secret.
An action fails after a variable or secret was deleted	The action still uses that key.	Recreate the key, or change the action so it no longer uses it.

Accounts and access

Symptom	Cause	Fix
You can sign in but see “You’re not linked to any project yet.”	The account has not been added to a project.	Ask an owner to link you, or a project admin to add you under Access.
Forgotten password	The system sends no recovery email.	Ask an owner to Reset password on your user detail page.
“Too many wrong current-password attempts. Try again in N minutes.”	The current password was entered wrongly several times while changing it.	Wait until the lockout period ends, or ask an owner to reset your password.
Unexpectedly signed out on a device	The password was just changed or reset elsewhere.	Sign in again with the new password.
“You haven’t been granted access to this environment.”, or prod is missing from the environment switcher	The environment is restricted and you have not been granted access.	Ask an admin to grant access on the Environments page.
“In prod, this page needs the Editor role or higher”	Your maximum role in that environment is below what the page needs.	Pick another environment in the top bar, or ask an admin.
“This page needs the Admin role or higher”	Your project role is below what the page needs.	Ask a project admin.

Administration

Symptom	Cause	Fix
Saving the IP allowlist is refused	Your current IP is not on the new list.	Click Add my IP and save again.
Deleting an action, view or data source is blocked: “Still in use in the places above — remove it from there first, then delete again.”	The item is still used by a JS action, a view or another action’s param (for a data source: by actions).	Remove it from the listed places, then delete again.
A schedule turned itself off	The person the schedule runs as was removed from the project, lost access to the environment, or was deleted.	An editor re-enables the schedule. From then on, it runs with that editor’s permissions.
“Couldn’t reach the server” or Executor unavailable	The platform is temporarily not responding.	Try again in a few minutes. If the error persists, contact support.