Body: <p>Drupal 9x, CiviCRM  5.56.0. Getting &quot;Cannot execute queue &quot;user_job_XXX&quot;. There is no associated UserJob.&quot; while contacts import from csv ( civicrm/import/contact?reset=1 ) Perhaps related to <a href="https://civicrm.stackexchange.com/questions/42771/upgrade-to-5-54-failed">this question</a>.
  Have had to manually add the job name ( from corresponded civicrm_queue ) to make  it work. However it would be nice to understand why this is happening: missing DB trigger because of unfinished update? Any word of advice please?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-12-16T18:26:50.917Z
Comments.Text: All that userjob stuff is pretty new so might be a bug. If you get the same error on https://dmaster.demo.civicrm.org then you should file an issue at https://lab.civicrm.org/dev/core/-/issues
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-12-16T18:28:54.633Z
Comments.Text: But if you mean your upgrade to 5.56 didn't complete and so the database tables are incomplete, then would need to go find the stack trace in ConfigAndLog from the upgrade fail.
Comments.UserDisplayName: Demerit
Tags: <import><data-import><drupal-9><csv>
Title: web import fails because of empty "name" column in "civicrm_user_job" table
ThreadText: # web import fails because of empty "name" column in "civicrm_user_job" table
  
  (Asked by: username_0 on 2022-12-16)
  
  Drupal 9x, CiviCRM 5.56.0. Getting "Cannot execute queue "user\_job\_XXX". There is no associated UserJob." while contacts import from csv ( civicrm/import/contact?reset=1 ) Perhaps related to [this question](https://civicrm.stackexchange.com/questions/42771/upgrade-to-5-54-failed).
  Have had to manually add the job name ( from corresponded civicrm\_queue ) to make it work. However it would be nice to understand why this is happening: missing DB trigger because of unfinished update? Any word of advice please?
  
  **Tags:** import, data-import, drupal-9, csv
  
  > **Comments:**
  > **username_1**: All that userjob stuff is pretty new so might be a bug. If you get the same error on https://dmaster.demo.civicrm.org then you should file an issue at https://lab.civicrm.org/dev/core/-/issues  
  > **username_1**: But if you mean your upgrade to 5.56 didn't complete and so the database tables are incomplete, then would need to go find the stack trace in ConfigAndLog from the upgrade fail.  
  
  ---
  
  ## 0 answers
  
  