Import Feedback Automation: Success Was Silent, So It Looked Like Nothing Happened

An interactive control that performs an action and then simply returns to its resting state, with nothing on screen acknowledging that anything happened, forces whoever clicked it into genuine uncertainty about what just occurred — did the action run and produce a genuinely uneventful result, or did the click itself fail to register or fail silently partway through? A human interacting with software relies overwhelmingly on visible feedback to distinguish those two very different situations; a control that behaves identically in both cases has, in effect, removed the one signal that would let anyone tell them apart, regardless of how correctly the underlying logic actually ran.

Handling an error case explicitly is often treated as the more urgent, more obviously necessary half of calling any service — an unhandled error can crash a page, leave a spinner stuck indefinitely, or otherwise produce a visibly broken experience that draws attention to itself during even a casual test. A successful response that is simply discarded produces no such visible breakage on its own: the action genuinely completed, no exception was thrown, and the interface returns cleanly to its resting state. That absence of any obvious symptom is exactly why a success path receiving no confirmation treatment at all can survive testing, review, and real usage for a meaningful stretch of time before someone notices the specific, quieter problem: not that anything crashed, but that nothing ever visibly happened.

Centriu Maestro's client-campaigns screen offers a button that calls a dedicated import service to pull a client's own campaigns directly from a connected advertising platform. That service, confirmed directly from its own existing implementation, already returned a structured result on every call — the number of campaigns newly imported, the number updated because they already existed, the number deliberately skipped, and a list of any specific errors encountered.

The button's own click handler, before this fix, awaited that result and then branched on exactly one condition: whether the result indicated an error had occurred. If so, an existing error banner displayed a message describing what went wrong. If not — meaning the import had genuinely succeeded — the handler's own code simply did nothing further at all, discarding the imported/updated/skipped counts the service had already computed and returned, with no banner, no confirmation, and no visible change of any kind reaching the screen.

The fix adds a success path that mirrors the existing error path's own visual pattern rather than inventing a new one: a success banner, styled consistently with the screen's own established error banner, now displays the service's real, returned result directly — the actual counts of what was imported, updated, and skipped — and automatically dismisses itself after five seconds so it does not linger indefinitely on screen. Alongside displaying the result, the handler now also triggers a refresh of the client list specifically when the result indicates something was genuinely imported or updated, so a list that would otherwise be showing stale data updates automatically to reflect what the import actually changed, without requiring a separate manual reload.

Verified live directly against the running application: clicking the import button for a client with no real advertising platform connected — the common, previously silent case — now displays a banner reading "Import complete: 0 new, 0 updated, 0 skipped," giving an explicit, accurate confirmation that the action genuinely ran and genuinely found nothing to import, rather than leaving that exact situation indistinguishable from the button having done nothing at all.

Before the fix, a vending machine correctly processed a payment and correctly dispensed an item every single time, but only ever lit up its display screen when something went WRONG — a jam, a declined card — leaving a person who inserted payment and received nothing wrong (because there was genuinely nothing to dispense) staring at a blank, unlit screen with no way to tell whether their payment had even registered. After the fix, the exact same successful, uneventful transaction now lights up the screen with a clear "transaction complete" message every time, regardless of whether anything was actually dispensed.

Centriu Maestro's campaign-import button now displays the real result of every import attempt, closing a gap where a successful run — including the common, unremarkable case of importing nothing because no real platform is connected — was indistinguishable on screen from the button having silently done nothing at all.

This automation covers specifically how Centriu Maestro's campaign-import button communicates its own result once an import attempt completes successfully. It is a distinct concern from this pillar's separate pages on how Maestro reflects a campaign's own status once it has genuinely been imported, paused, or removed on the connected advertising platform.

Handling a service's own error case explicitly, while leaving its success case entirely unhandled, correctly prevents the more visibly disruptive failure mode (an unhandled crash or an indefinitely stuck loading state) — and can pass casual review specifically because that visible failure mode is the one most likely to be noticed and tested for. Handling BOTH branches of a response — confirming success explicitly, not merely the absence of an error — is the only version of the two that gives a person reliable, complete feedback regardless of which branch an actual attempt takes.