@3dsource/metabox-modular-configurator-api
    Preparing search index...

    Type Alias CtaStatus

    CtaStatus: "started" | "ready" | "failed"

    Lifecycle of the GetCallToActionInformation workflow.

    Makes the CTA round trip observable. MetaBox posts the configuration to the callback URL from admin and acts on the reply itself — it navigates to the returned redirectUrl and reports an invalid reply in its own UI — so there is no url or payload to hand back. What the host page is missing is only whether the workflow started, completed, or failed.

    'started' — disable the CTA button and show a spinner; the POST is a network round trip to a third-party endpoint and can be slow. 'ready' — the callback answered and MetaBox is acting on it. 'failed' — the endpoint did not answer usably; re-enable the button and log it, since the customer's own backend is the thing at fault.

    Do not wait for a redirect url — MetaBox performs the navigation. Treat 'started' and 'failed' as the load-bearing states: on success the user is navigated away, so 'ready' may not be observed before the page unloads. Failure detail, when the configurator supplies any, arrives on statusMessageChanged rather than here.