An Export Stuck in "Assembling"

Assembling does not mean the core application is working. It means the file has left the core application and is waiting on an external renderer to call back when it's done. Once that handoff completes, the record flips to Assembling and the interface polls for updates every five seconds — but only while the Exports screen itself is loaded. A freshly created export isn't polled until you visit or reload that screen, so if you created the request and then navigated elsewhere, open or reload the Exports screen before concluding it's stuck.

That polling checks for a callback from the external service. If the callback never arrives — because of a crash, a dropped message, or a silent renderer-side failure that never learns where to send the result — the record sits in Assembling forever with nothing noticing. Nothing in the core application times out or retries that callback. There is no automatic recovery.

PDF exports (specifically, the Financial Activity Report) are handled by a different rendering service that sends its own explicit failure signal for most failure modes, including a self-enforced compute timeout. When a PDF render fails in a way the renderer itself can detect, the export status usually does resolve to an on-screen error rather than sitting in Assembling indefinitely. The gap is a failure abrupt enough that the renderer never learns where to send the callback — rare, but possible.

Excel exports use a different pipeline with no equivalent explicit failure path.

No in-product control exists to requeue or regenerate a stuck export — not for you, and not for support. The only action the system takes automatically is an internal, staff-only alert that fires if an export stays in Assembling past a threshold (typically around 30 minutes). That alert is purely observational; it changes nothing. Resolving a stranded export today requires manual staff intervention, and there is no staff UI for it either.

This means a customer's screen cannot distinguish "still legitimately rendering" from "silently dead." If your export has been in Assembling for more than 30 minutes, it is more likely dead than working.

Do not wait indefinitely or keep reloading the screen expecting it to finish. The genuinely useful alternative is:

1. Request a fresh export. The original stuck request does not block a new one, and the new one may succeed where the first did not.
2. If the second request also stalls, contact support rather than continuing to retry. Include:
   • The engagement name
   • Which export type you requested (e.g., Bank Transactions and All Item Details, Excel)
   • What time you requested it (or what time the stuck export shows as Requested)
   • Whether you applied any filters before exporting, and if so, which filters

Support can look at the specific request on the back end. They cannot regenerate the stuck one in place, but they can investigate whether something about your request (its size, the data it touches, the filters applied) is triggering the failure consistently. In some cases they may be able to act on the underlying issue rather than just telling you to retry.