Publish, pause, and resume your bot
Understand readiness, first publication, later updates, and the difference between saved files and live hosting.
Check what is ready
Publishing puts a particular validated version online. Open Overview or Deploy to see current readiness and blockers. A passing build, saved source, required database setup, platform configuration, account authorization, and billing eligibility may all matter. Resolve the stated blocker before trying again.
Completing the first platform connection can start the first eligible validated deployment automatically. Follow the publishing progress shown by the project. Later edits are saved for review, and the Publish update action applies the reviewed version to the live bot. Ability integration and website knowledge integration also need publication when they change the code.
Publish a reviewed update
- Finish the edit and read its saved result and checks.
- Check the connections and settings used by the new version.
- Review the current and published versions, then select Publish update or the publishing action offered in Deploy.
- Wait for publishing and health verification to finish. If a blocker or failure appears, read its current diagnosis.
- Open the bot on its platform and run the journey affected by the update.
After publishing starts, wait for the current health report and test the intended interaction. A running process can still have a feature or connection problem.
When a hosting billing check is pending
Hosting billing check pending means publishing was accepted, but billing still needs verified hosting or price information. Publishing can continue while that check retries separately. The pending billing check alone is not a deployment failure, and no unverified hosting charge is made.
Follow Deploy and Activity for the current publication and billing results. Do not republish or request a code repair solely because this billing check is pending. If the report says billing needs attention, follow its current instructions.
Pause or resume hosting
Pause stops hosting execution while keeping the project saved. Resume starts the runtime again when eligible. Pausing a WhatsApp bot pauses session work; saved connection information is preserved for resume where supported.
Hosting is charged from your wallet, separately from creating the bot and from services the bot calls. If usable funds run out, hosting has a 48-hour payment grace period while charges continue to accrue. Unpaid hosting can then be suspended. Read Hosting charges and the 48-hour grace period for the full payment and recovery steps.
Pausing is not deleting, and it does not reverse costs that were already incurred. A top-up does not resume a bot you paused yourself; use Resume when you are ready and billing requirements are met.
When you want to remove a bot
Use Pause for a temporary break. Permanent deletion removes the project and starts cleanup of its hosting and connections. Back up any source you want to keep before choosing it.