Process Activity Breaking

RE: Process Activity Breaking

divyak2994 — Thu, 27 Nov 2025 12:38:28 GMT

Now we replaced with subrpeocess which is having all sync records to start process its working fine now.Is it suggestable approach.

RE: Process Activity Breaking

divyak2994 — Wed, 26 Nov 2025 14:33:42 GMT

We are executing few sp' s from backend those are inserting few tables those records we needs to sync. For that we need identifier from the table to sync the corresponding record sync from record smart service . That's why we are querying the id by using query smart smart service.

RE: Process Activity Breaking

Jesse Knight — Tue, 25 Nov 2025 14:34:19 GMT

Is there any reason you're using the Query Database smart service over the others available?

Write Records will write and automatically sync your database row. It's a trivial thing to convert a map / CDT to the equivalent record.
Database operations that contain any sort of complexity in a large database will likely timeout at 10 seconds in the Query Database smart service
The Execute Stored Procedure smart service is far easier to configure, do advanced things with, and maintain
Any database functions that contain business logic should likely be refactored into Appian and applied before writing the data
- Unless they are explicitly for large scale ETL purposes
- Yet large scale ETL processes in the database are very likely to hit the 10 second timeout

RE: Process Activity Breaking

Mike Schmitt — Tue, 25 Nov 2025 14:30:45 GMT

You could probably increase the "chained efficiency" and thus decrease the user waiting by doing something more efficient with your multiple Sync Record smart services. And why are you using "Query Database" at all? I recommend against ever using that unless there's a critical need for something *only* it can do, which is very rare in my experience.

The Sync Record smart services, if they aren't **directly** needed for the next user-facing task, could be run in an asynchronous-style side process flow that will run simultaneously to the user's new task. This of course somewhat depends on what you're doing/showing/querying on your next user task, which you have not specified.

Can you post a screenshot of your process flow so far, or at least a general outline of it?

RE: Process Activity Breaking

Shubham Aware — Tue, 25 Nov 2025 12:22:02 GMT

AFAIK, Multiple activity-chained sync record smart services cause record locking conflicts and execution delays. Removing XOR gateways reduced complexity and execution time, preventing lock conflict and allowing the process to complete successfully.