Return stuck in processing

What "Processing" means

When you trigger Tax Prep for a return, Filed runs a multi-stage pipeline. Before Tax Prep begins, binder creation must already be complete - this step builds the client's document library from uploaded files and runs automatically when documents are uploaded. The Tax Prep pipeline stages then run in order:

• Backup import - reading the client's current state from the tax software

• Tax extraction - pulling field-level data from the documents

• Reconciliation - planning which fields to enter

• Data entry - writing values into the tax software

• Entry validation - confirming the entries landed correctly

The return shows "Processing" for the full duration of this pipeline.

For most returns the entire pipeline completes in a few minutes to around half an hour. A return that remains in Processing for several hours without reaching a completed or error state is worth investigating.

Common causes

The pop-up message Filed displays is always the most direct clue. Check it before working through the causes below.

Filed sync app not running (Drake and UltraTax only)

For Drake and UltraTax, Filed relies on the Filed Sync App - a desktop application installed on the machine where your tax software lives - to transfer the backup file between the local environment and Filed. The transfer stalls and the return stays in Processing indefinitely if the Sync App is:

• Closed

• On a machine that is offline or asleep

• Stopped after hitting an error

This is the most common cause of a stuck return for firms on Drake or UltraTax. If the Sync App is not actively running, the pipeline cannot advance past the backup stage.

Missing prior-year return

In some workflows Filed needs the client's prior-year return to complete processing. If no prior-year file has been uploaded to the client's document folder, the pipeline pauses waiting for it, which can appear as a return stuck in Processing.

Temporary system hiccup

Occasionally a transient infrastructure event or queue delay causes the pipeline to stall on a particular step. The return stays in a running state even though no persistent underlying problem exists. Clicking Re-run Tax Prep is usually all that is needed to clear this.

Deeper processing failure

In rare cases one of the pipeline sub-tasks (such as document conversion, tax extraction, or the data-entry bot session) fails in a way that does not surface a clear user-facing error. The task record stays in a running state rather than transitioning to failed. These cases require engineering review to diagnose from the internal logs.

How to fix it

The right action depends on the cause identified above.

If you are on Drake or UltraTax, first confirm the machine where the Sync App is installed is on and reachable. Check whether the Sync App is actively running and look for any error messages inside the app itself.

If a prior-year return is missing, upload it to the client's document folder and then click Re-run Tax Prep.

For a transient hiccup, click Re-run Tax Prep and wait for the pipeline to complete.

If the return is still in Processing after Re-run Tax Prep has been attempted and a reasonable wait has passed, the issue is likely a deeper processing failure and needs support.

When to contact support

Reach out to Filed support if the return is still showing Processing after you have clicked Re-run Tax Prep and waited at least 30 minutes. Include:

• The return ID

• Your tax software name and version

• Whether you checked the Sync App and what you found (Drake and UltraTax only)

• The full text of any pop-up or error message Filed displayed