Review code and restore versions

Inspect saved files, use checkpoints, and restore a previous source version with care.

Use saved checkpoints

Versions records saved source checkpoints. BOTS SI edits use checkpoints so you can review changes and return to earlier code. Some completed chat edits also offer Undo or Restore this version. Identify the version by its time, description, and short reference before restoring.

  1. Open Versions or the completed edit in chat.
  2. Choose the checkpoint that represents the behavior you want to recover.
  3. Read the confirmation. CookMyBots safeguards the current files before restoring the selected source.
  4. After restoration, inspect and validate the result. Publish the intended version separately when required.

Restoring source does not rewind customer records, authorizations, wallet transactions, or sent messages. Describe a saved-data problem separately.

Where saved source and recovery fit

Project files are saved in the CookMyBots workspace. Saved build source bundles and checkpoints provide additional recovery evidence when available. GitHub is an optional, separate source backup; connecting GitHub is not what enables workspace version history.

A temporary build sandbox is an execution environment, not your source backup. Its expiry does not by itself mean your saved project was deleted. A live deployment, saved project source, customer records, and a GitHub repository are separate things.

If files appear missing, confirm the signed-in account and project first. Check the saved builds and Versions, then follow the available recovery action or contact support with the project reference and approximate time. Recovery needs an available source bundle or checkpoint that matches the project and saved version. A version entry alone does not prove its files remain recoverable. Avoid starting a replacement build or overwriting partial files while the missing source is being investigated.

Keep an independent copy of your project source

Inspect and edit files

Code gives technical users a view of project files. Available tools may include an advanced editor for manual changes. Save intentional edits and check the result before publishing. Some managed files are protected, so use the supported controls or ask BOTS SI when a file cannot be edited directly.

Keep manual changes focused and explain them in your next request. Saving a file does not mean it passed build checks.