Skip to main content
miquell290189
October 10, 2025
Solved

Issue with “Delete Document” node right after Integration upload

  • October 10, 2025
  • 10 replies
  • 0 views

Hi everyone,

I'm running into an unexpected issue when trying to delete a document immediately after uploading it through an integration in the same process model.

I have an interface where the user uploads an Excel file, which gets stored temporarily in Document Management.
From that interface, I start a Process Model that looks like this (see attached image):

  1. Start Node

  2. Gateway → checks if a document exists

  3. HTTP Integration (CEDT_INT_postUpload) → sends the file to an external endpoint

  4. Delete Document → deletes the temporary file after upload

  5. End Node

When the process reaches the Delete Document node, it seems that Appian hasn’t finished handling or streaming the document yet.
As a result, the integration fails or the file never actually reaches the destination folder.

If I remove the Delete Document node (or move it to a later step, e.g., after a short delay or in a separate subprocess), everything works fine — the upload completes successfully.

Has anyone experienced something similar?
Is it possible that Appian still locks or streams the file during the integration, causing the Delete Document node to interfere?
Are there any best practices for safely deleting documents after uploading them through an integration in the same process?

Best answer by shubhama926776

Deleting the document immediately after an integration can interfere with file streaming due to Appian not releasing the file lock, so delay deletion (using a timer or subprocess) until the integration has finished processing.

10 replies

stefanhelzle0001
October 10, 2025

I do expect that any file upload is finalized when that node completes. I suggest to open a support case to discuss this.

shubhama926776
October 10, 2025

Deleting the document immediately after an integration can interfere with file streaming due to Appian not releasing the file lock, so delay deletion (using a timer or subprocess) until the integration has finished processing.

stefanhelzle0001
October 10, 2025

[mention:6b9f80ff18f9420082d13ef2d5121d56:e9ed411860ed4f2ba0265705b8793d05] do you have any insights? My understanding is, that a process node behaves in an atomic transactional behaviour. The behaviour reported here violates this..

stefanhelzle0001
October 10, 2025

 [mention:6b9f80ff18f9420082d13ef2d5121d56:e9ed411860ed4f2ba0265705b8793d05] do you have any insights? My understanding is, that a process node behaves in an atomic transactional behaviour. The behaviour reported here violates this..

mikes0011
Brainy
October 10, 2025

is there an echo in here? [emoticon:bfea11b94cc048458ee2c01f963db38d]

peter.lewis
October 10, 2025

Ha don't worry I got the ping! I haven't personally heard of this happening before - I'd open a support ticket like Stefan suggested above.

chandrasekharg0001
October 11, 2025

Curious to know The error was showing at the CEDT_INT_postUpload Node. and the path did not reached the Delete document as well. 
1. Try to check you uploading a documents with different Names.(Does not makes sense here, but curious that the document might got deleted before you even call the intergration).

2. Isn't a good idea to process the output of the Integration check the success path and Delete document to that success path?