### To run failed [work job](https://github.com/samvera-labs/bulkrax/blob/main/app/jobs/bulkrax/import_work_job.rb) from the [rails console](#user-content-to-get-to-the-rails-console-in-the-web-container)
# Sometimes, we have to decrement the failed count if it fails again, as it increases the failed count, but the job has already been counted as failed.
```
### To run failed [fileset job](https://github.com/samvera-labs/bulkrax/blob/main/app/jobs/bulkrax/import_file_set_job.rb) from the [rails console](#user-content-to-get-to-the-rails-console-in-the-web-container)
# Sometimes, we have to decrement the failed count if it fails again, as it increases the failed count, but the job has already been counted as failed.
The reason why these counts are important, is because the scheduled relationship job will not run if any of the work, fileset or collection jobs are pending. Sometimes, all of the jobs finish successfully, but the importer has got messed up with the count and so will keep waiting.
To run failed [collection job](https://github.com/samvera-labs/bulkrax/blob/main/app/jobs/bulkrax/import_collection_job.rb) from the [rails console](#user-content-to-get-to-the-rails-console-in-the-web-container)
```
i = Bulkrax::ImportCollectionJob.new
entry = 15
importer = 1
i.perform(entry, importer)
```
### To run [scheduled relation job](https://github.com/samvera-labs/bulkrax/blob/main/app/jobs/bulkrax/schedule_relationships_job.rb) from the [rails console](#user-content-to-get-to-the-rails-console-in-the-web-container)