• Every Pro feature vanished after I updated the free plugin. The add-on is older than the floor the core sets (Cascade Forge Pro 1.6.7 for free 1.8.6). It is kept from starting rather than left half-running: it adds no steps and no events, and a flow that uses a Pro step fails with “unknown action”. A red admin notice, shown to users who can update plugins, names the installed version and the required one. If Dashboard → Updates lists no update for the add-on, download it from the downloads page of your Avakode dashboard and upload it over the installed copy in Plugins → Add New Plugin → Upload Plugin. Everything returns; saved flows and run history are untouched.
• Cascade Forge Pro does not start and asks for a newer Cascade Forge. Cascade Forge Pro 1.6.7 needs Cascade Forge 1.8.6 or newer. Its red notice names the installed core version; download Cascade Forge from the downloads page of your Avakode dashboard and upload it over the installed copy in Plugins → Add New Plugin → Upload Plugin, and the add-on starts on the next page load.
• A flow did not fire. Check that it is active, then check Runs — a run that exists but failed is a different problem from no run at all. Scheduled work depends on wp-cron, which needs traffic.
• A step keeps failing. Open the run and read the step’s error. After three attempts the run goes to the Failed view, where the step, the error and a masked payload preview are shown and “Retry from failed step” starts a new run at that step.
• “Retry” is refused with “the flow has changed”. That is deliberate: the saved step list was rebuilt after the failure, so the recorded position no longer points at the same step. Re-run the flow from the top, or restore the version the run executed from Flow history first.
• An approval e-mail never arrived. The run is not lost. It wakes at its own expiry and reads the ledger; if nobody has answered by then, on_timeout decides (rejection by default). Check the site’s mail delivery, and note that the links stop working once the request has expired or has already been answered.
• The same approval link was clicked twice. Only the first click counts — the decision UPDATE is conditional on the row still being undecided.
• A parameter shows as a JSON box instead of a form. The builder found something it could not draw without risking data: a key not in the schema, a nested condition group, or an OR group on a site without the Pro add-on. The panel says which; edit the JSON and the rest of the form is unaffected.
• A recipe has no Import button. Its reason is printed on the card: either a step comes from the Pro add-on that is not installed, or the neighbouring plugin the trigger belongs to is not active.
• A webhook ran twice. It should not: deliveries are de-duplicated on an event hash. If the sender changes the payload between retries the hash changes too — ask them to send a stable idempotency key.
• A condition never matches. Operators have names (greater_than, not >), and an unknown operator never matches by design.
• “Draft the flow” says it will spend credits. It will — 3 of them. The recipe library next door costs nothing.