> ## Documentation Index > Fetch the complete documentation index at: https://docs.flokitai.com/llms.txt > Use this file to discover all available pages before exploring further. # Action queue > Review, approve, and track FloKit's growth recommendations. The action queue is FloKit's recommendation surface. FloKit continuously analyzes your payback data and surfaces prioritized growth actions — budget moves, creative pauses, audience shifts, offer tests, and paywall experiments. Every action enters the queue in draft state and requires human review before execution. Nothing runs without approval. FloKit action queue showing approved and reviewed growth recommendations *** ## Action types | Type | Example | Typical impact | | -------------------- | ---------------------------------------------------- | ------------------------------------------------- | | `budget_shift` | Reallocate \$5k/week from Campaign A to Campaign B | ROAS improvement within 7 days | | `creative_pause` | Pause 3 creatives with declining trial conversion | 10–15% improvement in conversion-weighted ROAS | | `audience_shift` | Exclude low-LTV lookalike segment | Reduces spend waste on high-churn cohorts | | `offer_test` | Test 7-day trial vs 14-day trial on annual plan | Identify which trial length drives higher renewal | | `paywall_experiment` | A/B test paywall copy for annual vs monthly emphasis | Measure conversion impact of plan emphasis | | `bid_adjustment` | Raise target CPA for markets with strong payback | Scale volume in proven markets | *** ## Action lifecycle Every action moves through a defined set of states. No state can be skipped. ```mermaid theme={null} stateDiagram-v2 [*] --> draft: FloKit generates action draft --> draft: Guardrail check fails (reason attached) draft --> ready_for_approval: All guardrail checks pass ready_for_approval --> approved: Team member approves approved --> running: Action executed running --> completed: Full duration, no rollback running --> rolled_back: Rollback trigger breached or manual rollback completed --> [*] rolled_back --> [*] ``` **`draft`** FloKit has generated the action but is still running guardrail checks. Actions in this state are not visible in the approval queue. If a guardrail check fails, the action stays in draft with a reason attached. **`ready_for_approval`** All guardrail checks passed. The action is visible in the queue and waiting for your review. This is where you spend most of your time in the queue. **`approved`** A team member approved the action. If the ad platform write access is connected, FloKit will execute the action automatically. If write access is not connected, FloKit provides the exact steps to execute manually. **`running`** The action is live. FloKit is monitoring the outcome metrics — CAC, ROAS, trial conversion — against the expected impact and rollback triggers. **`completed`** The action ran its full intended duration and was not rolled back. Outcome metrics are recorded and attributed to the action in action outcome reports. **`rolled_back`** The action triggered a rollback condition — either automatically (if auto-rollback is configured) or manually. Rollback reason and outcome delta are stored for review. *** ## Guardrails Every action is checked against your configured guardrails before entering the `ready_for_approval` state. Actions that would: * Breach a daily or weekly spend cap * Modify a campaign or ad set marked as excluded * Fall below your minimum confidence threshold * Belong to an action type you've disabled ...stay in `draft` and never reach the approval queue. You'll see a guardrail summary on any action that was held. See [Guardrails](/product/guardrails) for configuration details. *** ## Approving actions **Dashboard** Go to **Actions**, select any action in `ready_for_approval` state, review the signal, expected impact, and rollback condition, then click **Approve**. **API** ```bash theme={null} POST https://YOUR-FLOKIT-API-HOST/v1/actions/{id}/approve ``` Optionally include a note in the request body: ```json theme={null} { "note": "Approved after manual review of 90-day ROAS for Campaign B." } ``` **Slack** If the Slack integration is enabled, FloKit sends a notification when a new action enters `ready_for_approval`. You can approve or reject directly from Slack without opening the dashboard. Available during private beta. *** ## Rollback If an approved action causes a performance regression — defined by your rollback trigger thresholds — FloKit flags the action in the dashboard and can execute a rollback automatically if configured. Default rollback signal: CAC increases more than 20% relative to the pre-action baseline, measured over a 72-hour window after the action goes live. **Manual rollback:** ```bash theme={null} POST https://YOUR-FLOKIT-API-HOST/v1/actions/{id}/rollback ``` Rollback reverts the specific change FloKit made on the ad platform (e.g. restores previous budget allocation or un-pauses a creative). It does not undo any downstream effects from the period the action was live. See [Guardrails](/product/guardrails#rollback-triggers) for configuring automatic rollback. *** ## What FloKit never does automatically Regardless of guardrail configuration or automation settings, FloKit will not: * **Change pricing** on any subscription plan. * **Modify paywall configuration** — copy, layout, or plan ordering. * **Adjust subscription offers** — trial lengths, discount amounts, or promotional offers. * **Exceed budget guardrails** — the spend cap is a hard ceiling, not a soft recommendation. These actions are blocked at the platform level. Write access to ad platforms requires explicit configuration per platform and grants FloKit access only to campaign budget and bid parameters — not to product or pricing systems.