KB-2307 Engine disconnect "Unable to append transaction *** for to the transaction log"

Ryan Good — Tue, 21 May 2024 17:16:30 GMT

Current Revision posted to Appian Knowledge Base by Ryan Good on 5/21/2024 5:16:30 PM

Symptoms

Engines disconnect with the following exception inside the service_manager.log:

YYYY-MM-DD HH:MM:SS,mmm [TransactionLogHandler-<engine>-99-1] ERROR com.appian.komodo.translog.TransactionLogHandler - Unable to append transaction ######### for <engine> to the transaction log [EngineRequest{updateFlag=true, functionName=performEngineWork, params=null, credentials=null, localeId=, timeZoneId=, timestampInteger=-#########, timestampDouble=-#########, randomInteger=#########, isForMigration=false, transactionId=0, interfaceName=PROCESS, shard=null, engineTopologyName=null, apiVersion=9, correlationId=[-34, -106, 76, -8, -64, 5, 64, 101, -120, -27, -120, -66, 84, -39, -18, 9]}]
com.appian.komodo.translog.TransactionSequenceException: ######### is not the next transaction id in the sequence after #########
 at com.appian.komodo.log.KafkaTransactionLogService.append(KafkaTransactionLogService.java:187) ~[core-1.236.29.jar:1.236.29]
 at com.appian.komodo.translog.TransactionLogHandler.persistRequestToLog(TransactionLogHandler.java:201) ~[core-1.236.29.jar:1.236.29]
 at com.appian.komodo.translog.TransactionLogHandler.lambda$channelRead$0(TransactionLogHandler.java:180) ~[core-1.236.29.jar:1.236.29]
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_252]
 at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_252]
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_252]
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_252]
 at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.46.Final.jar:4.1.46.Final]
 at java.lang.Thread.run(Thread.java:748) [?:1.8.0_252]
YYYY-MM-DD HH:MM:SS,mmm [TransactionLogHandler-execution01-99-1] ERROR com.appian.komodo.translog.TransactionLogHandler - Writing failed inflight request to .l file
YYYY-MM-DD HH:MM:SS,mmm [KomodoEventBus-58103] ERROR com.appian.komodo.engine.connection.KProcessManager - Terminal engine fault received for <engine>. Killing K process. [event received: TransactionAppendFailedEvent{createdInstant=YYYY-MM-DDTHH:MM:SS.mmmZ, engineId=execution01, transactionId=#########}]
YYYY-MM-DD HH:MM:SS,mmm [KomodoEventBus-58149] ERROR com.appian.komodo.engine.EngineSupervisor - Received terminal engine fault: TransactionAppendFailedEvent{createdInstant=2020-07-17T16:42:59.611Z, engineId=<engine>, transactionId=#########}

The engine is able to recover in a few minutes:

YYYY-MM-DD HH:MM:SS,mmm [KomodoEventBus-58212] INFO com.appian.komodo.engine.status.EngineStatusMonitor - <engine> is now EngineStateAndMode{engineState=RUNNING, mode=PRIMARY}

Cause

Another process is accessing the log files which the K engine is trying to write to. On Windows, another process having the file open will completely prevent K from writing to the file. This can force the engine into a bad state and cause the above error.

Action

Disable any other processes from accessing the files which the K engines write to. In particular, customers using Windows have seen this issue when running some sort of file scanner (often an antivirus or security tool) which scans Appian files. For more information, please refer to the relevant documentation.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: May 2024

Tags: engines, infrastructure

[DRAFT SP-4956] KB-XXXX Engine disconnect "Unable to append transaction *** for to the transaction log"

Ryan Good — Fri, 03 May 2024 20:53:29 GMT

Revision 9 posted to Appian Knowledge Base by Ryan Good on 5/3/2024 8:53:29 PM

Symptoms

Engines disconnect with the following exception inside the service_manager.log:

YYYY-MM-DD HH:MM:SS,mmm [TransactionLogHandler-<engine>-99-1] ERROR com.appian.komodo.translog.TransactionLogHandler - Unable to append transaction ######### for <engine> to the transaction log [EngineRequest{updateFlag=true, functionName=performEngineWork, params=null, credentials=null, localeId=, timeZoneId=, timestampInteger=-#########, timestampDouble=-#########, randomInteger=#########, isForMigration=false, transactionId=0, interfaceName=PROCESS, shard=null, engineTopologyName=null, apiVersion=9, correlationId=[-34, -106, 76, -8, -64, 5, 64, 101, -120, -27, -120, -66, 84, -39, -18, 9]}]
com.appian.komodo.translog.TransactionSequenceException: ######### is not the next transaction id in the sequence after #########
 at com.appian.komodo.log.KafkaTransactionLogService.append(KafkaTransactionLogService.java:187) ~[core-1.236.29.jar:1.236.29]
 at com.appian.komodo.translog.TransactionLogHandler.persistRequestToLog(TransactionLogHandler.java:201) ~[core-1.236.29.jar:1.236.29]
 at com.appian.komodo.translog.TransactionLogHandler.lambda$channelRead$0(TransactionLogHandler.java:180) ~[core-1.236.29.jar:1.236.29]
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_252]
 at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_252]
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_252]
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_252]
 at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.46.Final.jar:4.1.46.Final]
 at java.lang.Thread.run(Thread.java:748) [?:1.8.0_252]
YYYY-MM-DD HH:MM:SS,mmm [TransactionLogHandler-execution01-99-1] ERROR com.appian.komodo.translog.TransactionLogHandler - Writing failed inflight request to .l file
YYYY-MM-DD HH:MM:SS,mmm [KomodoEventBus-58103] ERROR com.appian.komodo.engine.connection.KProcessManager - Terminal engine fault received for <engine>. Killing K process. [event received: TransactionAppendFailedEvent{createdInstant=YYYY-MM-DDTHH:MM:SS.mmmZ, engineId=execution01, transactionId=#########}]
YYYY-MM-DD HH:MM:SS,mmm [KomodoEventBus-58149] ERROR com.appian.komodo.engine.EngineSupervisor - Received terminal engine fault: TransactionAppendFailedEvent{createdInstant=2020-07-17T16:42:59.611Z, engineId=<engine>, transactionId=#########}

The engine is able to recover in a few minutes:

YYYY-MM-DD HH:MM:SS,mmm [KomodoEventBus-58212] INFO com.appian.komodo.engine.status.EngineStatusMonitor - <engine> is now EngineStateAndMode{engineState=RUNNING, mode=PRIMARY}

Cause

Action

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: May 2024

Tags: engines, infrastructure

[DRAFT SP-4956] KB-XXXX Engine disconnect "Unable to append transaction *** for to the transaction log"

pauline.delacruz — Tue, 16 Apr 2024 21:03:01 GMT

Revision 8 posted to Appian Knowledge Base by pauline.delacruz on 4/16/2024 9:03:01 PM

Symptoms

Engines disconnect with the following exception inside the service_manager.log:

YYYY-MM-DD HH:MM:SS,mmm [TransactionLogHandler-<engine>-99-1] ERROR com.appian.komodo.translog.TransactionLogHandler - Unable to append transaction ######### for <engine> to the transaction log [EngineRequest{updateFlag=true, functionName=performEngineWork, params=null, credentials=null, localeId=, timeZoneId=, timestampInteger=-#########, timestampDouble=-#########, randomInteger=#########, isForMigration=false, transactionId=0, interfaceName=PROCESS, shard=null, engineTopologyName=null, apiVersion=9, correlationId=[-34, -106, 76, -8, -64, 5, 64, 101, -120, -27, -120, -66, 84, -39, -18, 9]}]
com.appian.komodo.translog.TransactionSequenceException: ######### is not the next transaction id in the sequence after #########
 at com.appian.komodo.log.KafkaTransactionLogService.append(KafkaTransactionLogService.java:187) ~[core-1.236.29.jar:1.236.29]
 at com.appian.komodo.translog.TransactionLogHandler.persistRequestToLog(TransactionLogHandler.java:201) ~[core-1.236.29.jar:1.236.29]
 at com.appian.komodo.translog.TransactionLogHandler.lambda$channelRead$0(TransactionLogHandler.java:180) ~[core-1.236.29.jar:1.236.29]
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_252]
 at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_252]
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_252]
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_252]
 at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.46.Final.jar:4.1.46.Final]
 at java.lang.Thread.run(Thread.java:748) [?:1.8.0_252]
YYYY-MM-DD HH:MM:SS,mmm [TransactionLogHandler-execution01-99-1] ERROR com.appian.komodo.translog.TransactionLogHandler - Writing failed inflight request to .l file
YYYY-MM-DD HH:MM:SS,mmm [KomodoEventBus-58103] ERROR com.appian.komodo.engine.connection.KProcessManager - Terminal engine fault received for <engine>. Killing K process. [event received: TransactionAppendFailedEvent{createdInstant=YYYY-MM-DDTHH:MM:SS.mmmZ, engineId=execution01, transactionId=#########}]
YYYY-MM-DD HH:MM:SS,mmm [KomodoEventBus-58149] ERROR com.appian.komodo.engine.EngineSupervisor - Received terminal engine fault: TransactionAppendFailedEvent{createdInstant=2020-07-17T16:42:59.611Z, engineId=<engine>, transactionId=#########}

The engine is able to recover in a few minutes:

YYYY-MM-DD HH:MM:SS,mmm [KomodoEventBus-58212] INFO com.appian.komodo.engine.status.EngineStatusMonitor - <engine> is now EngineStateAndMode{engineState=RUNNING, mode=PRIMARY}

Cause

Another process is accessing the log files which the K engine is trying to write to. On Windows, a different process having the file open will prevent K from writing to the file, which puts the engine into a bad state causing this error.

Action

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: April 2024

Tags: engines, infrastructure

[DRAFT SP-4956] KB-XXXX Engine disconnect "Unable to append transaction *** for to the transaction log"

pauline.delacruz — Fri, 05 Apr 2024 15:10:45 GMT

Revision 7 posted to Appian Knowledge Base by pauline.delacruz on 4/5/2024 3:10:45 PM

Symptoms

Engines disconnect with the following exception inside the service_manager.log:

YYYY-MM-DD HH:MM:SS,mmm [TransactionLogHandler-<engine>-99-1] ERROR com.appian.komodo.translog.TransactionLogHandler - Unable to append transaction ######### for <engine> to the transaction log [EngineRequest{updateFlag=true, functionName=performEngineWork, params=null, credentials=null, localeId=, timeZoneId=, timestampInteger=-456218220, timestampDouble=-5280.303480879629, randomInteger=1886317636, isForMigration=false, transactionId=0, interfaceName=PROCESS, shard=null, engineTopologyName=null, apiVersion=9, correlationId=[-34, -106, 76, -8, -64, 5, 64, 101, -120, -27, -120, -66, 84, -39, -18, 9]}]
com.appian.komodo.translog.TransactionSequenceException: ######### is not the next transaction id in the sequence after #########
 at com.appian.komodo.log.KafkaTransactionLogService.append(KafkaTransactionLogService.java:187) ~[core-1.236.29.jar:1.236.29]
 at com.appian.komodo.translog.TransactionLogHandler.persistRequestToLog(TransactionLogHandler.java:201) ~[core-1.236.29.jar:1.236.29]
 at com.appian.komodo.translog.TransactionLogHandler.lambda$channelRead$0(TransactionLogHandler.java:180) ~[core-1.236.29.jar:1.236.29]
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_252]
 at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_252]
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_252]
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_252]
 at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.46.Final.jar:4.1.46.Final]
 at java.lang.Thread.run(Thread.java:748) [?:1.8.0_252]
YYYY-MM-DD HH:MM:SS,mmm [TransactionLogHandler-execution01-99-1] ERROR com.appian.komodo.translog.TransactionLogHandler - Writing failed inflight request to .l file
YYYY-MM-DD HH:MM:SS,mmm [KomodoEventBus-58103] ERROR com.appian.komodo.engine.connection.KProcessManager - Terminal engine fault received for <engine>. Killing K process. [event received: TransactionAppendFailedEvent{createdInstant=YYYY-MM-DDTHH:MM:SS.mmmZ, engineId=execution01, transactionId=#########}]
YYYY-MM-DD HH:MM:SS,mmm [KomodoEventBus-58149] ERROR com.appian.komodo.engine.EngineSupervisor - Received terminal engine fault: TransactionAppendFailedEvent{createdInstant=2020-07-17T16:42:59.611Z, engineId=<engine>, transactionId=#########}

The engine is able to recover in a few minutes:

YYYY-MM-DD HH:MM:SS,mmm [KomodoEventBus-58212] INFO com.appian.komodo.engine.status.EngineStatusMonitor - <engine> is now EngineStateAndMode{engineState=RUNNING, mode=PRIMARY}

Cause

Action

In order to prevent this from happening, disable any other processes from accessing the files which the K engines write to. In particular, customers using Windows have seen this issue when running some sort of file scanner (often an antivirus or security tool) which scans Appian files. For more information, please refer to the documentation.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: April 2024

Tags: engines, infrastructure

[DRAFT SP-4956] KB-XXXX Engine disconnect "Unable to append transaction *** for to the transaction log"

pauline.delacruz — Fri, 05 Apr 2024 15:09:52 GMT

Revision 6 posted to Appian Knowledge Base by pauline.delacruz on 4/5/2024 3:09:52 PM

Symptoms

Engines disconnect with the following exception inside the service_manager.log:

YYYY-MM-DD HH:MM:SS,mmm [TransactionLogHandler-<engine>-99-1] ERROR com.appian.komodo.translog.TransactionLogHandler - Unable to append transaction ######### for <engine> to the transaction log [EngineRequest{updateFlag=true, functionName=performEngineWork, params=null, credentials=null, localeId=, timeZoneId=, timestampInteger=-456218220, timestampDouble=-5280.303480879629, randomInteger=1886317636, isForMigration=false, transactionId=0, interfaceName=PROCESS, shard=null, engineTopologyName=null, apiVersion=9, correlationId=[-34, -106, 76, -8, -64, 5, 64, 101, -120, -27, -120, -66, 84, -39, -18, 9]}]
com.appian.komodo.translog.TransactionSequenceException: ######### is not the next transaction id in the sequence after #########
 at com.appian.komodo.log.KafkaTransactionLogService.append(KafkaTransactionLogService.java:187) ~[core-1.236.29.jar:1.236.29]
 at com.appian.komodo.translog.TransactionLogHandler.persistRequestToLog(TransactionLogHandler.java:201) ~[core-1.236.29.jar:1.236.29]
 at com.appian.komodo.translog.TransactionLogHandler.lambda$channelRead$0(TransactionLogHandler.java:180) ~[core-1.236.29.jar:1.236.29]
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_252]
 at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_252]
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_252]
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_252]
 at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.46.Final.jar:4.1.46.Final]
 at java.lang.Thread.run(Thread.java:748) [?:1.8.0_252]
YYYY-MM-DD HH:MM:SS,mmm [TransactionLogHandler-execution01-99-1] ERROR com.appian.komodo.translog.TransactionLogHandler - Writing failed inflight request to .l file
YYYY-MM-DD HH:MM:SS,mmm [KomodoEventBus-58103] ERROR com.appian.komodo.engine.connection.KProcessManager - Terminal engine fault received for <engine>. Killing K process. [event received: TransactionAppendFailedEvent{createdInstant=YYYY-MM-DDTHH:MM:SS.mmmZ, engineId=execution01, transactionId=#########}]
YYYY-MM-DD HH:MM:SS,mmm [KomodoEventBus-58149] ERROR com.appian.komodo.engine.EngineSupervisor - Received terminal engine fault: TransactionAppendFailedEvent{createdInstant=2020-07-17T16:42:59.611Z, engineId=<engine>, transactionId=#########}

The engine is able to recover in a few minutes:

YYYY-MM-DD HH:MM:SS,mmm [KomodoEventBus-58212] INFO com.appian.komodo.engine.status.EngineStatusMonitor - <engine> is now EngineStateAndMode{engineState=RUNNING, mode=PRIMARY}

Cause

This error is caused by another process accessing the log files which the K engine is trying to write to. On Windows, a different process having the file open will prevent K from writing to the file, which puts the engine into a bad state causing this error.

Action

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: April 2024

Tags: engines, infrastructure

[DRAFT SP-4956] KB-XXXX Engine disconnect "Unable to append transaction *** for to the transaction log"

pauline.delacruz — Fri, 29 Mar 2024 20:51:34 GMT

Revision 5 posted to Appian Knowledge Base by pauline.delacruz on 3/29/2024 8:51:34 PM

Symptoms

This section is required for this template. All symptoms of the issue, including relevant screenshots and log lines, should be included here. The symptoms should be as descriptive as possible.

Following is the main exception:

2020-07-17 16:42:59,442 [TransactionLogHandler-execution01-99-1] ERROR com.appian.komodo.translog.TransactionLogHandler - Unable to append transaction 35259884 for execution01 to the transaction log [EngineRequest{updateFlag=true, functionName=performEngineWork, params=null, credentials=null, localeId=, timeZoneId=, timestampInteger=-456218220, timestampDouble=-5280.303480879629, randomInteger=1886317636, isForMigration=false, transactionId=0, interfaceName=PROCESS, shard=null, engineTopologyName=null, apiVersion=9, correlationId=[-34, -106, 76, -8, -64, 5, 64, 101, -120, -27, -120, -66, 84, -39, -18, 9]}]
com.appian.komodo.translog.TransactionSequenceException: 35259884 is not the next transaction id in the sequence after 35259882
 at com.appian.komodo.log.KafkaTransactionLogService.append(KafkaTransactionLogService.java:187) ~[core-1.236.29.jar:1.236.29]
 at com.appian.komodo.translog.TransactionLogHandler.persistRequestToLog(TransactionLogHandler.java:201) ~[core-1.236.29.jar:1.236.29]
 at com.appian.komodo.translog.TransactionLogHandler.lambda$channelRead$0(TransactionLogHandler.java:180) ~[core-1.236.29.jar:1.236.29]
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_252]
 at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_252]
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_252]
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_252]
 at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.46.Final.jar:4.1.46.Final]
 at java.lang.Thread.run(Thread.java:748) [?:1.8.0_252]
2020-07-17 16:42:59,447 [TransactionLogHandler-execution01-99-1] ERROR com.appian.komodo.translog.TransactionLogHandler - Writing failed inflight request to .l file
2020-07-17 16:42:59,615 [KomodoEventBus-58103] ERROR com.appian.komodo.engine.connection.KProcessManager - Terminal engine fault received for execution01. Killing K process. [event received: TransactionAppendFailedEvent{createdInstant=2020-07-17T16:42:59.611Z, engineId=execution01, transactionId=35259884}]
2020-07-17 16:42:59,615 [KomodoEventBus-58149] ERROR com.appian.komodo.engine.EngineSupervisor - Received terminal engine fault: TransactionAppendFailedEvent{createdInstant=2020-07-17T16:42:59.611Z, engineId=execution01, transactionId=35259884}

Engine is able to recover in a few minutes:

2020-07-17 16:45:12,148 [KomodoEventBus-58212] INFO com.appian.komodo.engine.status.EngineStatusMonitor - execution01 is now EngineStateAndMode{engineState=RUNNING, mode=PRIMARY}

Cause

Action

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: March 2024

Tags: engines, infrastructure

[DRAFT SP-4956] KB-XXXX Engine disconnect "Unable to append transaction *** for to the transaction log"

pauline.delacruz — Fri, 29 Mar 2024 20:50:18 GMT

Revision 4 posted to Appian Knowledge Base by pauline.delacruz on 3/29/2024 8:50:18 PM

Symptoms

This section is required for this template. All symptoms of the issue, including relevant screenshots and log lines, should be included here. The symptoms should be as descriptive as possible.

Cause

Action

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: March 2024

Tags: engines, infrastructure

[DRAFT SP-4956] Engine disconnect "Unable to append transaction *** for execution01 to the transaction log"

pauline.delacruz — Tue, 26 Mar 2024 18:40:15 GMT

Revision 3 posted to Appian Knowledge Base by pauline.delacruz on 3/26/2024 6:40:15 PM

Symptoms

This section is required for this template. All symptoms of the issue, including relevant screenshots and log lines, should be included here. The symptoms should be as descriptive as possible.

Cause

This error is caused by another process accessing the log files which the K engine is trying to write. On Windows a different process having the file open will prevent K from writing to the file which puts the engine into a bad state causing this error. In order to prevent this from happening the customer can disable any other processes from accessing the files which the K engines write to. In particular other Windows customers have seen this issue when running some sort of file scanner (often an antivirus or security tool) which scans Appian files.

Action

This section is required for this template and contains the steps to resolve the issue. If an issue in an article is solved by a hotfix and/or major version of Appian, use the following language to indicate that:

Apply the latest hotfix to your Appian installation.
Upgrade to the latest version of Appian.
Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

If there is a product issue with Engineering that is open and a workaround for that issue exists, include it in the Action section until the fix is available. After the fix is made available, use that as a workaround instead.

Otherwise, the content in this section should wholly solve a customer’s issue without producing any undesirable side effects. If there is at least one valid action that doesn’t cause undesirable side effects, all other actions with negative side effects should go in the Workaround section.

If there is no action or workaround that resolves the issue, use the following language:

There is no action or workaround currently available for this issue. If you are facing this issue, please open a support case with Appian.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: March 2024

Tags: engines, infrastructure

[DRAFT SP-4956] Engine disconnect "Unable to append transaction *** for execution01 to the transaction log"

pauline.delacruz — Tue, 26 Mar 2024 18:39:58 GMT

Revision 2 posted to Appian Knowledge Base by pauline.delacruz on 3/26/2024 6:39:58 PM

Symptoms

This section is required for this template. All symptoms of the issue, including relevant screenshots and log lines, should be included here. The symptoms should be as descriptive as possible.

Cause

Action

Apply the latest hotfix to your Appian installation.
Upgrade to the latest version of Appian.
Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

If there is no action or workaround that resolves the issue, use the following language:

There is no action or workaround currently available for this issue. If you are facing this issue, please open a support case with Appian.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: March 2024

[DRAFT SP-4956] Engine disconnect "Unable to append transaction *** for execution01 to the transaction log"

pauline.delacruz — Tue, 26 Mar 2024 18:37:49 GMT

Revision 1 posted to Appian Knowledge Base by pauline.delacruz on 3/26/2024 6:37:49 PM

Symptoms

This section is required for this template. All symptoms of the issue, including relevant screenshots and log lines, should be included here. The symptoms should be as descriptive as possible.

Cause

This section is required for this template. When writing a cause for a particular article, ensure the following is taken into consideration:

The cause is concise and does not disclose more information than absolutely necessary.
The cause does not share any Appian source code. Source code for plugins/shared components are fine.
If this is an issue outside of the Appian product and the third-party vendor included documentation referencing the bug, provide their documentation for reference.

For any enhancements/defects, use one of the following as applicable:

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-XXXXX.
This product use case has been logged to the Appian Product Team for consideration to add this functionality in the product. Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.
This issue has been hotfixed via AN-XXXXX in Appian X.X.
This issue has been hotfixed via AN-XXXXX in Appian X.X to X.X.
This use case has been incorporated in Appian X.X.
This use case has been incorporated in Appian X.X to X.X.

When logging a product defect, ensure you use the known issues tag as well as the open issues or fixed issues tag, depending if the issue is fixed or not.

If no cause is known and this is not something Engineering can reproduce/needs to know about, then say “The root cause of this issue is currently unknown.” If you use that as your cause, then a valid action must be present.

Action

Apply the latest hotfix to your Appian installation.
Upgrade to the latest version of Appian.
Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

If there is no action or workaround that resolves the issue, use the following language:

There is no action or workaround currently available for this issue. If you are facing this issue, please open a support case with Appian.

Workaround

This section is optional and should only be used as an alternative action if there is a massive technical debt associated with performing the action in the above section for customers (such as upgrading). It can also be used if there is a solution to the issue in the article but is more inconvenient to implement or it causes other undesirable behavior and wouldn’t warrant being an action.

Affected Versions

This section includes any relevant version information for Appian or other third/party configurations. Some examples of valid affected versions are as follows:

This article applies to all versions of Appian.
This article applies to all self-managed versions of Appian.
This article applies to all versions of Appian Cloud.
This article applies to Appian 7.11 and later.
This article applies to Appian 16.2 and earlier.
This article applies to Appian 7.11 and 16.1.
This article applies to Appian 16.1, 16.2, and 16.3.
This article applies to self-managed Appian 19.3 and earlier.
This article applies to all versions of Appian from Appian 7.10 to Appian 16.2.
This article applies to all versions of Appian using JBoss EAP 6.4.9 as an application server and Internet Explorer 9 as a web browser.

Last Reviewed: Month YYYY