Loading screen after record action

Synchronous Process Execution: If the related action is triggered through a process model that performs operations synchronously, Appian may display a "loading" screen while it completes. This is especially noticeable if the process includes complex logic, queries, or integrations.
Solution: Consider making the process asynchronous if possible. For straightforward updates, you can use Appian's Write to Data Store Entity smart service and then return control quickly to the user interface.

Delay Due to Expressions or Rule Execution: If there are complex expression rules or interfaces being evaluated after the action is taken, they may cause delays.
Solution: Simplify any expression rules or minimize calculations during execution. Optimize interfaces to reduce the loading impact.

Form Submission Behavior: If your action triggers form submission with validations or interactions causing reloading, it may contribute to delays.
Solution: Evaluate whether the form submission can be optimized or whether a simpler, alternative mechanism can update the record.

Network or System Load: The loading screen may also be a sign of network latency or an overloaded system.
Solution: Check the system's performance metrics and consider optimizing processes, queries, or operations