Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!

The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.

WEB API process model restart and error handling

Certified Associate Developer

I have a web API which expects post request and provides the response after completing few important nodes and other actions are configured Asynchronously . Asynchronous process involves copy document, send data to second external system which are wrapped as multiple subprocesses. Now let's say if any of these asych process fails and I notify the first external system along with process ID, is there a way possible to retrigger the appian broken instance again (ignore the failure reason)? if not can I restart from the broken node itself? does appian provide this capability?

(Plugins: Get Processes By Node Status and process-management-services doesn't seem to be working as expected for my case)

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer

    In Appian, you cannot restart a failed process instance or resume from a specific node once it has errored or completed.
    Instead, the recommended approach is to design retry logic—store the required data and trigger a new process or subprocess to re-run only the failed steps.
    To make this safe, ensure your integrations are idempotent and state is tracked, so retries don’t cause duplicate or inconsistent results.

Reply
  • 0
    Certified Lead Developer

    In Appian, you cannot restart a failed process instance or resume from a specific node once it has errored or completed.
    Instead, the recommended approach is to design retry logic—store the required data and trigger a new process or subprocess to re-run only the failed steps.
    To make this safe, ensure your integrations are idempotent and state is tracked, so retries don’t cause duplicate or inconsistent results.

Children
No Data