Skip to content

Message Reference

How to use this document

Search (Ctrl+F) for the exact message text you see on screen. Each entry answers:

  • Where it appears
  • What triggered it
  • What it means
  • What to do

Toast notifications

Toast notifications appear in the bottom-right corner of the screen. They disappear automatically after a few seconds. SQL Cor uses its own toast system — separate from Creatio’s native notifications.


✅ Success toasts (green background)


"Settings saved"

PropertyValue
WhereBottom-right toast
Color🟢 Green
Triggered byChanging any slider value or toggle in System Settings tab
MeansThe new setting value was saved to the database successfully
What to doNothing — change applied immediately, no restart needed

"Rule added"

PropertyValue
WhereBottom-right toast
Color🟢 Green
Triggered bySaving a new rule in Grant Access dialog OR Add Rule (blacklist) dialog
MeansThe new access rule or blacklist rule was created successfully
What to doNothing — rule is active immediately

"Rule updated"

PropertyValue
WhereBottom-right toast
Color🟢 Green
Triggered bySaving changes in the Edit rule dialog
MeansThe existing rule was modified successfully
What to doNothing — changes applied immediately

"Database connection established (X ms)"

PropertyValue
WhereBottom-right toast
Color🟢 Green
Triggered byClicking Check Connection in Service Actions
MeansSQL Cor successfully reached the database. X ms = round-trip latency.
What to doNothing — connection is working normally

Latency interpretation:

ValueMeaning
< 50msExcellent
50–200msNormal
200–500msAcceptable
> 500msSlow — investigate server load or network

"Deleted: X records"

PropertyValue
WhereBottom-right toast
Color🟢 Green
Triggered byConfirming Clear Logs action in Service Actions
MeansX audit log records were permanently deleted
What to doNothing — audit log is now empty. Cannot be undone.

❌ Error toasts (red background)


"Network error"

PropertyValue
WhereBottom-right toast
Color🔴 Red
Triggered byAny action that requires a backend request when the network is unavailable
MeansSQL Cor could not reach the backend server — network issue between browser and Creatio server
What to doCheck your internet connection. Try refreshing the page. If problem persists, contact your IT administrator.

"No database connection"

PropertyValue
WhereBottom-right toast
Color🔴 Red
Triggered byCheck Connection action OR any query execution when DB is down
MeansThe Creatio backend can be reached, but it cannot connect to the database
What to doContact your database administrator. This is a server-side issue, not a browser issue.

"403 access denied" (or equivalent 403 error message)

PropertyValue
WhereBottom-right toast
Color🔴 Red
Triggered byAny action when your Creatio session has expired or your admin privileges were revoked mid-session
MeansThe server rejected the request because your current session doesn’t have permission
What to doLog out and log back in. If problem persists, contact your administrator — your admin role may have been removed.

Results panel messages

These appear inside the Results panel (below the editor), not as toasts.


Execution success messages


"X rows returned in Y ms"

PropertyValue
WhereResults panel — meta info below table
Triggered bySuccessful SELECT query
MeansQuery completed. X = row count returned. Y = execution time in milliseconds.
NoteIf X is capped by Max Rows setting, you’ll also see the limit notice below.

"X rows changed in Y ms"

PropertyValue
WhereResults panel — meta info
Triggered bySuccessful DML query (INSERT / UPDATE / DELETE)
MeansQuery completed. X = number of rows affected. Y = execution time.

"Statement executed successfully. (Y ms)"

PropertyValue
WhereResults panel
Triggered bySuccessful DDL query (CREATE / ALTER / DROP)
MeansDDL statement completed without errors

Row limit notices


"Results limited to X rows. Use LIMIT in your query for precise control."

PropertyValue
WhereResults panel — below the data table
Triggered bySELECT returned more rows than the configured Max Rows limit
MeansYou’re seeing only the first X rows. More exist in the database but were not returned.
What to doAdd LIMIT n to your query to get exactly the rows you need. Or ask your administrator to raise the Max Rows setting.

Execution error messages

These appear in red in the Results panel when a query fails.


"Access denied. Your access level is Read-only. This operation requires DML access."

PropertyValue
WhereResults panel
Triggered byReadOnly user attempting INSERT, UPDATE, or DELETE
MeansYour current access level (ReadOnly) does not permit data modification
What to doContact your administrator to request DML access if your work requires it

"Access denied. Your access level is DML. This operation requires DDL access."

PropertyValue
WhereResults panel
Triggered byDML user attempting CREATE, ALTER, or DROP
MeansYour current access level does not permit schema changes
What to doContact your administrator to request DDL access if your work requires it

"This query is blocked by the system. Reason: [description]"

PropertyValue
WhereResults panel
Triggered byQuery matches a blacklist rule (system or manual)
MeansThe query was rejected before reaching the database. [description] = the reason text your administrator wrote when creating the rule.
What to doRead the reason. If you believe the block is incorrect, contact your administrator. If it’s a system rule (hardcoded), it cannot be overridden.

Examples of blocked reasons you might see:

  • "Direct access to SysUser is restricted. Use User Management in Creatio instead."
  • "Schema changes require a change request. Contact DBA team."
  • "SQL Server shell execution is never allowed."

"Query execution timeout exceeded."

PropertyValue
WhereResults panel
Triggered byQuery ran longer than the configured Query Timeout setting
MeansThe database forcibly stopped the query because it exceeded the time limit
What to doOptimize your query (add WHERE clause, use indexes). Or ask admin to increase timeout in System Settings.

"Multi-statement queries are not allowed for Read-only access."

PropertyValue
WhereResults panel
Triggered byReadOnly user submitting a query with multiple statements separated by ;
MeansFor security, ReadOnly users must submit one SQL statement at a time
What to doSplit your query — run each statement separately

Database engine errors (PostgreSQL / MSSQL)

These are error messages that come directly from the database — not from SQL Cor. They appear in red in the Results panel.

Error textCommon causeFix
relation "X" does not existTable name wrong case or missing quotesUse double quotes: "TableName". Check Smart Hints.
column "Y" does not existColumn name typo or wrong caseCheck column names with information_schema.columns
syntax error at or near "..."SQL syntax mistake at the indicated positionReview your SQL near the quoted text
column reference "X" is ambiguousSame column name in multiple joined tablesAdd table alias: t."ColumnName"
permission denied for table XDB-level permission issueContact administrator — this is below SQL Cor’s access control
value too long for type character varying(N)Inserting text longer than the column allowsShorten the value or check the correct column
duplicate key value violates unique constraintInserting a value that already exists in a unique/primary key columnCheck existing values before inserting
null value in column "X" violates not-null constraintInserting NULL into a required fieldProvide a value for the required column
foreign key constraint violationReferencing a row that doesn’t exist in the parent tableEnsure the referenced record exists first

Maintenance Mode message


"[Administrator's custom message]"

PropertyValue
WhereResults panel (replaces normal results)
Triggered byAny query execution attempt when Maintenance Mode is ACTIVE
MeansAn administrator has temporarily disabled query execution for maintenance. The message text is customized by your admin.
Example messages"Database update in progress until 14:00. Please try again later." · "Monthly backup running. Available in ~30 minutes."
What to doWait and try again later. Contact your administrator for updates.

Dialogs — confirmation messages

These appear as popup dialogs that require you to click a button before proceeding. They are shown before any irreversible action.


User-facing dialogs (Terminal page)


Destructive Operation dialog

PropertyValue
WhereModal popup over the Terminal page
Triggered bySubmitting a query containing DELETE when Dry Run is OFF
TextWarning about destructive operation + preview of query
PurposeForce conscious decision before permanent data deletion
ButtonAction
ConfirmProceeds with DELETE execution
CancelCloses dialog — nothing happens, query stays in editor

Admin dialogs (Administration page)


"Revoke this access? The user will lose access immediately."

PropertyValue
WhereConfirmation popup
Triggered byClicking Revoke 🚫 on an active access rule
MeansYou are about to deactivate this rule. The user/role loses SQL Cor access immediately. The rule record stays in the table as Revoked.
ButtonAction
RevokeDeactivates the rule immediately
CancelCloses dialog — rule unchanged

"Delete this access rule permanently? This cannot be undone."

PropertyValue
WhereConfirmation popup
Triggered byClicking Delete 🗑️ on any access rule
MeansYou are about to permanently remove this record from the database
ButtonAction
DeletePermanently removes the rule
CancelCloses dialog — rule unchanged

"Delete this blacklist rule? Queries matching this pattern will no longer be blocked."

PropertyValue
WhereConfirmation popup
Triggered byClicking Delete 🗑️ on a manual blacklist entry
MeansRemoving this rule means the previously blocked pattern will now be allowed
ButtonAction
DeleteRemoves the blacklist rule permanently
CancelCloses dialog — rule unchanged

"Clear all logs? This action cannot be undone."

PropertyValue
WhereConfirmation popup
Triggered byClicking Clear Logs in Service Actions
MeansAll audit log records will be permanently deleted. There is no way to recover them.
ButtonAction
ClearDeletes all audit log records immediately
CancelCloses dialog — logs unchanged

Smart Hints messages

These appear in the yellow bar above the Results panel automatically after certain errors.


Case-sensitive hint

Message: "PostgreSQL is case-sensitive. Try wrapping the table name in double quotes: "Account""

PropertyValue
Triggered byError: relation "X" does not exist
MeansYour table name was not in double quotes, so PostgreSQL lowercased it
INSERT INTO EDITOR✅ Available — rewrites query with quoted table name

TOP vs LIMIT hint

Message: "On PostgreSQL, use LIMIT instead of TOP. Example: SELECT * FROM "Table" LIMIT 10"

PropertyValue
Triggered byQuery contains SELECT TOP N syntax
MeansMSSQL-style syntax detected — PostgreSQL uses LIMIT instead
INSERT INTO EDITOR✅ Available — converts query automatically

Permission hint

Message: "Permission error. Check your access level in Administration → Access Control."

PropertyValue
Triggered byDatabase-level permission denied error
MeansThe database rejected the query at the DB level (different from SQL Cor’s access control)
INSERT INTO EDITOR❌ Not available — informational only
What to doContact your SQL Cor administrator

Ambiguous column hint

Message: "Column is ambiguous. Add the table alias prefix: t."ColumnName""

PropertyValue
Triggered byError: column reference "X" is ambiguous
MeansMultiple joined tables have a column with the same name — PostgreSQL doesn’t know which one
INSERT INTO EDITOR✅ Available — provides corrected query template with aliases

Status indicator states

These appear in the footer status indicator (bottom-left of page).

IconTextMeaningAction
🟢ConnectedDatabase is reachable and respondingNone needed
🔴DisconnectedDatabase cannot be reachedUse Check Connection in Admin · Contact DBA
🟡CheckingConnection test in progressWait a moment

Cross-references

TopicSee
What causes each errorTroubleshooting
Where each UI element isFeature Reference
How access levels workUser Guide
Admin toast notifications listAdmin Guide
How to manage access rulesAdmin Guide

SQL Cor — Secure SQL Workbench for Creatio. Free and open source. License: MIT.

Document v1.0 · Applies to SQL Cor v1.0 · Last updated 1 June 2026