# Common Autosubmit commands | Command | Description | Autosubmit documentation | | --------- | ----------- | ------------------------ | | expid | Add a new experiment to the database and create the corresponding directory. | [documentation](https://autosubmit.readthedocs.io/en/master/userguide/create/index.html#create-an-experiment) | | create | Read the configuration and create the workflow for the experiment. | [documentation](https://autosubmit.readthedocs.io/en/master/userguide/configure/index.html#how-to-configure-experiments) | | run | Run the workflow. Usually this is called in the background. | [documentation](https://autosubmit.readthedocs.io/en/master/userguide/run/index.html#running-experiments) | | monitor | Use this to get the current status of the workflow. Works both when the workflow is running (i.e. an `autosubmit run` runs in the background) and when not. | [documentation](https://autosubmit.readthedocs.io/en/master/userguide/monitor_and_check/index.html#how-to-monitor-an-experiment) | | setstatus | Set the status of one or multiple jobs. This is useful e.g. if a job failed, you fixed the problem and now you want to start from there again. Some examples are [below](#setting-job-status) | [documentation](https://autosubmit.readthedocs.io/en/master/userguide/manage/index.html#how-to-change-the-job-status) | | inspect | Create all the scripts for the configured jobs and places them in the `tmp` directory. You can use this, if you are not sure that e.g. all parameter replacements worked. | [documentation](https://autosubmit.readthedocs.io/en/master/userguide/monitor_and_check/index.html#how-to-generate-cmd-files) | | refresh | Update the project repository.
**CAUTION: it clones the *auto-icon* repository from scratch. Local changes to the configuration will be lost!**
You might want to consider doing a `git pull` within the cloned repository instead. | [documentation](https://autosubmit.readthedocs.io/en/master/userguide/manage/index.html#how-to-synchronize-with-the-project-s-latest-changes) | | recovery | If something went horribly wrong and your workflow is in an ill-defined state, use this to recover your experiment. | [documentation](https://autosubmit.readthedocs.io/en/master/userguide/modifying_workflow/index.html#how-to-restart-the-experiment) | ## Setting job status You can set the status of arbitrary jobs in your workflow to an arbitrary value (e.g. `WAITING`, `READY` or `COMPLETED`) by using the `autosubmit setstatus` command. A few examples shall illustrate common use cases: Set all failed jobs in your workflow to `WAITING` (e.g. to re-run the jobs): ``` autosubmit setstatus -fs FAILED -t WAITING -s -np ``` Set all `RUN_ICON` jobs in your workflow to `WAITING` (e.g. to re-run the jobs): ``` autosubmit setstatus -ft RUN_ICON -t WAITING -s -np ``` Set the `BUILD_ICON` and `BUILD_PYTHON` jobs in your workflow to `COMPLETED` (e.g. because they were running successfully already but you had to run `autosubmit create` again): ``` autosubmit setstatus -ft "BUILD_ICON BUILD_PYTHON" -t COMPLETED -s -np ``` Suspend job `t001_2004010100_default_1_RUN_ICON` of expid `t001` to delay execution: ``` autosubmit setstatus t001 -fl t001_2004010100_default_1_RUN_ICON -t SUSPENDED -s -np ``` Further details can be found in the [official documentation](https://autosubmit.readthedocs.io/en/master/userguide/manage/index.html#how-to-change-the-job-status).