Facing issue with default setting of timer trigger setting time in seconds

RE: Facing issue with default setting of timer trigger setting time in seconds

Stefan Helzle — Tue, 26 May 2026 06:46:35 GMT

Did you consider to start a process every 5 minutes which then consumes more than one message?

Or, it spawns multiple processes consuming multiple messages?

You just have to make sure to consume each message only once. In such scenarios, I tend to use DB locking tables.

RE: Facing issue with default setting of timer trigger setting time in seconds

Harsha Sharma — Tue, 26 May 2026 06:44:58 GMT

Instead of timer, have the pending events queried in batches in the process model. For processing have a separate process where you can pass the batch data and complete processing for multiple events in parallel. Loop through the batches and processing sub process by clearing/hiding unnecessary pvs for better memory management.

Not sure, what sort of processing is taking place. If its data related then see if in database itself store procedures/ triggers can help achieve the same instead of Appian process.

RE: Facing issue with default setting of timer trigger setting time in seconds

subhankar-Maantic — Tue, 26 May 2026 04:10:23 GMT

You probably do not need a polling process. At the end of WebAPi process you can trigger the 2nd process and it should have a condition if the previous instance is running do no initiate a 2nd DB query process.

Most efficient solution could be using kafka integration in 26.4

RE: Facing issue with default setting of timer trigger setting time in seconds

shivakanthreddyp0001 — Tue, 26 May 2026 00:23:28 GMT

Hi akshantr0678
Did you look at this transaction manager solution Appian Community