Recently active topics

HI , on email smart service “from” dropdown in addition to the options specified in documentation there is also 2 entries that are environment specific (ie they are correctly updated when i deploy to a different environment.) Where is the associated email address of these email  displays stored. I can’t find it in the custom.properties file or in admin console.  Thanks very much

While executing the process at runtime, the document upload to the dynamically created SharePoint folder is failing. I am using the Client Credentials authentication method with Client ID, and the following error is encountered during the document upload operation.[title=SharePoint returned a 404 HTTP error, message=SharePoint returned the following error code: -2147024893, System.IO.DirectoryNotFoundException, detail=File Not Found.]

I am having request to create new custom schema and export the data from default Appian schema   I too see some above recommendations in the earlier discussion, based on my analysis i found below solutions like  1) we can rename existing Appian table to new schema.table name which would move all the existing Appian table to new schema with out breaking its existing links RENAME TABLE  appian.my_table TO target_schema.my_table; 2) we can then use Appian default capabilities to change the source table in the corresponding records  via GUIIs this solution Okie to use , will it have any negative impact to look out ?, or do u have any other easy recommended way of doing this in appian ?

Is there a way to get the information in UI apart from designer for object comparison results modified in last 1 week by particular resource?Senior leadership wants to see report on Appian resource productivity and how many object being changed and what changes they are doing in some UI report instead of going into dashboard. They need to showcase the tracking possibility without going into designer.

SymptomsSystem Administrator account requires reactivation in the Appian Cloud environment. No active System Administrator account is available for native authentication. Users are unable to log in to the Appian Cloud environment. System Administrator account is locked due to too many failed login attempts.CauseThe System Administrator account is locked due to too many failed login attempts. Since the Unlock Accounts Automatically option is disabled in the Admin Console, the account remains locked and cannot be unlocked automatically after the default 30-minute lock duration. Additionally, SSO is enabled, preventing native authentication, and the Enable Forgot Password from Sign-In Page option is disabled, blocking password reset functionality.ActionPlease reach out to an authorized Support Contact in your organization who can create a Support Case with Appian Support for further assistance.Affected VersionsThis article applies to all versions of Appian Cloud.Last Reviewed: October 202

Hi Everyone, Just checking if anyone has come across this issue, when I try to drag and drop emails directly from the new outlook into document upload function it doesnt do anything. Same feature works fine when I drag and drop emails out of classic outlook.  

After upgrading SQL To Excel Smart Service to 2.1.6 version, the smart service generates the excel file and preserves the template formatting, but the mapped cell values are missing. We rely on cell key and cell value mapping to populate the data. It was working fine in 1.3.0 version.

Hello everyone! Just a quick question,  how should I prepare for it? Is retaking the Appian Developer Learning Path quizzes enough, or should I practice with other types of tests as well? Any advice would be greatly appreciated! Thanks in advance!

3043 ms peak average - MVS Export CDT to Excel (0005e34f-02ca-8000-6ee0-010000010000) -> Export Data Store Entity to Excel ( Health Check report) Export Data Store Entity to Excel smart service is taking too long to convert what will be the alternative of this service to replace with.

Can we add emojis in paragraph field?

creating new appian

How can I initiate the SFTP in Appian Designer? Are there any built-in Plugins available like HTTP or Appian RPA to initiate the SFTP? How can I connect AWS with the Process Model in Appian and make the data interactive between them?

SymptomsThe Control Panel does not appear in the Menu Page or navigation bar after Case Management Studio (CMS) is deployed. User is added to both CMGT Case Managers and Control Panel Users groups but still cannot access Control Panel. CMS deployment shows conflicts or errors during installation process that mention SYSTEM_RECORD_TYPE_USER: YYYY-MM-DD HH:MM:SS.mmm ERROR recordType <uuid> The recordType [id= uuid=<uuid>] was not imported because a required precedent is missing: recordField [uuid=SYSTEM_RECORD_TYPE_USER_FIELD_username location=List > Edit List] in record type [id=1 uuid=SYSTEM_RECORD_TYPE_USER] cannot be found. (APNX-1-4070-005) (APNX-1-4071-006)   CauseThe System User Record Type was not updated to a modern record type format, causing the Case Management Studio deployment to fail or become incomplete. Legacy record types are incompatible with CMS functionality and prevent the Control Panel from appearing in the Menu Page.ActionNavigate to the System User

SymptomsUser enters an invalid date value (e.g., 22/33/2026 or 22/55/8566) in a date field. Appian displays validation error: The value [invalid date] is not a valid date. Valid format is dd/mm/yyyy. Programmatic attempts to clear or update the field value using button actions with saveInto logic fail to remove the validation error. The validation error persists on the UI until the user manually edits or clears the field.CauseThis is the intended product design for a!dateField. The date field maintains an internal load variable that persists even when the value parameter changes. This internal load variable is only set to null when the value parameter is set to a valid date. Until value is a valid and non-null date, the internal load variable continues to be used, causing the validation error to persist.ActionIf you would like to be added to the Product Enhancement Request for this behavior, please raise a Support Case referencing the relevant existing product enhancement: #7020 - Date

SymptomsThe Health Check report flags two Appian-supported plugins as high-risk under the infrastructure category:People Functions (psshared.peoplefunctions) references private and deprecated Appian APIs Content Tools (com.appiancorp.ps.plugins.contenttools) references private Appian APIsBoth plugins display a risk finding INFR-0060 ("Plug-ins using removed, private or deprecated Appian APIs") in the Health Check Report.CauseThe plugins are using deprecated and/or private Appian APIs.ActionNo action is required. The plugins continue to function as expected, and per the plugin support policy, the latest available version of both plugins is supported. Ensure both plugins remain on their latest versions.To request suppression of risk finding INFR-0060 for Appian-Supported Plug-ins, please open a support case to request addition to Product Enhancement Request #9478 - Suppress Health Check Warnings for Supported Plugins. This enhancement request has been logged to the Appian Product Team fo

SymptomsUser accounts are locked after fewer failed login attempts than configured in the Admin Console.The default user account lockout threshold is configured to 6 failed login attempts in the Admin Console.User account is locked after only 3 failed login attempts. The 'Locked' flag appears on the user's profile after 3 failed attempts instead of the configured 6 attempts. Issue is reproducible consistently across multiple environments.CauseThis issue has been reported to the Appian Product Team. The reference number for this issue is AP-40258.Failed login attempts are occasionally registered and counted twice in the system, causing the account to lock after half the configured threshold. For example, if the lockout limit is set to 6 attempts, the account locks after 3 actual failed login attempts because each attempt is counted twice internally.ActionThere is no action currently available for this issue. If you are facing this issue, please open a support case with Appian Support.Wo

Kafka Tools upgraded from 1.4.3 to 1.7.0 and getting error message - SSL handshake failed while publishing message

SymptomsWhen users launch an Appian site, the browser displays a permission prompt requesting to "Access other devices on your local network" with options to Allow or Block. This behavior affects all users and occurs across multiple browsers (Chrome and Edge).CauseThis prompt is triggered by a Google Chrome feature that detects when a site attempts to make a connection to a user's local network (IP addresses such as 192.168.0.0/16 or 127.0.0.0/8). This can happen with services which modify a user's traffic such as VPN.ActionContact your internal teams to review services that might trigger Chrome's security feature and adjust accordingly.Affected VersionsThis article applies to all versions of Appian.Last Reviewed: August 2026

SymptomsThe a!agentChatField() component displays a perpetual "thinking" animation with no updates after sending a request to the agent. The agent successfully completes execution as verified in the Monitor tab, but the front-end UI component never reflects the completion. The outputsSaveInto parameter does not execute, and no data is returned to local variables in the UI. Debug mode shows no tool calls or information returned to the calling agentChat component. This behavior occurs consistently across all locations, for example: start forms, static site interfaces, designer preview, and blank unsaved interfaces.CauseThe issue is caused by a corporate network proxy or VPN blocking the response traffic from Appian's agent streaming endpoints. The proxy intercepts or blocks the network traffic required for the a!agentChatField() component to receive streaming responses from the agent execution backend.ActionConfigure your corporate network proxy or VPN to allowlist the Appian agent strea

SymptomsApplication server crashes when a user opens the Process History diagram of a specific process instance. Site slowness or unresponsivenessCauseWhen the Process History diagram is loaded, the engine retrieves all history records for the instance before paging. If the instance contains a very large process variable (commonly a list-type PV repeatedly appended to, or a PV that has grown to hundreds of MB / several GB), generating these history entries becomes extremely memory and CPU-intensive, exhausting heap.ActionThere is no action or workaround currently available for this issue. If you are facing this issue, please open a support case with Appian to identify the problematic instance.WorkaroundAvoid opening the Process History diagram for instances known or suspected to have very large process variables. Simply viewing history can trigger or worsen the condition. Mark large or unnecessary process variables as Hidden, which excludes them from process history and reports. See th

In Step#2 Exercise for Acme sport rental equipment,in step 14:In the right pane, under the prompt "Do you have documents related to Rental Requests?", click GENERATE RECORD TYPE. ○ Record Type Name: Enter W#ER Rental Agreement. ○ Click GENERATE.getting below error when tried to Generate, The System Has Encountered an ErrorHTTP Code: 500 APNX-1-4198-000 Error Evaluating UI Expression Expression evaluation error [evaluation ID = 3T01X] : [valid:false,syntaxError:false,value:Expression evaluation error: An error occurred while executing a save: Expression evaluation error at function fn!objectReadAction_appian_internal [line 4]: could not execute statement]

SymptomsUsers cannot create records from any data source backed by this database. While tables may be created in the database, they will see the following error in the frontend: Failed to configure your record type.Additionally, the following message will appear in tomcat-stdOut.log:YYYY-MM-DD HH:mm:ss,mss [ajp-nio-0.0.0.0-8009-exec-18] ERROR com.appiancorp.recordtypedesigner.functions.systemconnector.GetSourceSchemas - a!getSourceSchemascom.appiancorp.suiteapi.common.exceptions.AppianException: The data source [] was not found (APNX-1-4179-006)...Caused by: java.lang.RuntimeException: Datasource not found.CauseOn the database connected to Appian, lower_case_table_names is set to 1.ActionTo remediate, either of the two options can be used:Upgrade your install (recommended): This is a known issue resolved in Appian 25.3.825.0 and later. Set lower_case_table_names to 0: Please note that this cannot be set after the first startup of a database and a brand new database needs to be created.

SymptomsUsers cannot create Record Types from any data source backed by this database. They will see the following error in the frontend: Failed to configure your record type.Additionally, the following message will appear in tomcat-stdOut.log:YYYY-MM-DD HH:mm:ss,mss [ajp-nio-0.0.0.0-8009-exec-8] ERROR com.appiancorp.datasources.SqlExecutorImpl - Failed to execute the following statement against MySQL:insert into `<SCHEMA>`.`<TABLE>`(SORT_ORDER1, VALUE1, IS_ACTIVE1)    values        (1, 'Not Started', 1),        (2, 'In Progress', 1),        (3, 'Done', 1)Error: Field 'ID1' doesn't have a default valuejava.sql.SQLException: Field 'ID1' doesn't have a default valueCauseThe database connected to Appian is running in Strict Mode (STRICT_TRANS_TABLES or STRICT_ALL_TABLES is set), which prevents Appian from performing necessary schema/data operations.ActionOpen the MySQL configuration file (/etc/mysql/my.cnf on Linux or my.ini on Windows) and add or update the sql_mode directive

SymptomsTomcat fails during startup. The following error will appear in tomcat-stdOut.log:YYYY-MM-DD HH:mm:ss,mss [main] ERROR org.springframework.web.context.ContextLoader - Context initialization failedorg.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userActivityFilter' defined in ServletContext resource [/WEB-INF/conf/security/spring-security-01-common.xml]: Cannot resolve reference to bean 'userActivityService' while setting constructor argument...Caused by: java.lang.IllegalStateException: [jdbc/<PRIMARY SCHEMA>] Error during schema migration....Caused by: java.lang.IllegalStateException: liquibase.exception.CommandExecutionException: liquibase.exception.LiquibaseException: liquibase.exception.MigrationFailedException: Migration failed for changeset resources/appian/db/changelog/db-changelog-000002.xml::000002.3.1::appian:    Reason: liquibase.exception.DatabaseException: Multiple primary key defined [Failed SQL: (1068) ALTER TABLE Appi