Improvado Embedded API - Troubleshooting

The Improvado Embedded API connection and the accounts iframe behave in a few ways that are easy to read as a fault. These are the ones that come up most often.

A gap in the data after an account was switched off

Turning an account off on the accounts page pauses the extracts that use it, so nothing is collected for that account while it is off.

Turning it back on unpauses those extracts and triggers an extraction covering the period they were paused for, so the gap is filled rather than left as a hole in the data. If the missing rows have not appeared yet, that backfill is still running.

Re-enabling an account starts a long extraction

The backfill covers the whole period the account was switched off, so re-enabling an account that has been off for a long time starts a correspondingly long extraction.

It competes with scheduled work on the same connection and can delay regular runs. Plan the re-enable rather than reading the slowdown as a fault.

Only one toggle message arrives when several accounts are switched at once

The iframe posts a message to the parent window when accounts are toggled, so a host application can react without polling. Switching several accounts at once does not send one message per account: it sends a single AccountsBatched message for the batch, plus one AccountToggled for the first account in it.

Treat the event as a signal to re-read the account list rather than as a per-account notification. The payload is documented with the API in the Improvado Embedded API documentation.

Create Extract returned conflicted_orders

A successful Create Extract call can return a conflicted_orders array alongside the created extract. It is informational, not an error — the extract is created either way.

The array lists extraction orders that already cover the same account and report type as the one just requested, so a non-empty value is worth checking: two overlapping orders will both run and both write.