errors on auto-archive

[bennett landman]

I significant number of our scans (4/40ish) in the last batch are not auto-archived. When I look in the pre-archive, I see the sessions with status "ERROR". If I click, "reset", then (after a few minutes), the error status is cleared up. 

When I click archive, I see that these sessions match existing sessions. It seems that the first scan of a session was auto-archived, while the remaining 2 were skipped. Even if I click "append", I get an error. The only way that I can see to import this data is to create a new session name. 

Two questions: 

1) Is there a way that we can merge sessions after the fact. Move all scans and files for "XYZdup" to "XYZ". 

2) Is there a way to debug/fix the "append" process? It seems to be broken on our system. 

Thanks,

Bennett

[Timothy Olsen]

Ah ha!  I have a theory.  Is your AutoRun pipeline showing up in a failed state because it is failing to send emails at the end of the process?  If this is the case, then on the session report for the scans that were put in originally, you would see an error message about an AutoRun error.

The problem here is that the merge process fails if you are trying to merge to a session that is in an error state.  The failure to send the email causes the AutoRun to fail, which makes the session looks like it is in an error state.

To test if this is the problem, you can delete the failed workflow entry (instructions here: http://groups.google.com/group/xnat_discussion/browse_thread/thread/ad2c41e7e7db2304/b39e6f12439eb9fe?lnk=gst&q=delete+workflow+entry#b39e6f12439eb9fe).  Then, retry archiving the session. 

There are a few things we can do here (if this is the problem):

• Wait a few weeks until 1.6 is ready.  That will have an upgraded pipeline which should successfully send emails for you.  And then this problem should just go away.
• Delete all of the workflow entries for sessions that need to be merged.
• Modify the archive/merge logic to allow merging into sessions that have a failed archive process.  I think we actually intended to do this.  The Project -> Manage -> Prearchive settings menu has 3 options (prearchive all, auto-archive for append only, and auto-archive even when overwriting).  The idea here was that you could choose option 2 to auto-archive when nothing is odd, but leave data in the prearchive for manual review when something was unexpected.  Option 3 would ignore unexpected things and always auto-archive.  I think option 3 should ignore failed pipeline exceptions.  If it doesn't, then that is a bug.

What is the prearchive setting of your projects?  Does removing the failed workflow entries allow you to merge the sessions?

Tim

--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To view this discussion on the web visit https://groups.google.com/d/msg/xnat_discussion/-/BuNuJRgua8cJ.
To post to this group, send email to xnat_di...@googlegroups.com.
To unsubscribe from this group, send email to xnat_discussi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/xnat_discussion?hl=en.

[bennett landman]

After running for several weeks, it looks like removing the e-mail has cleared the error flags. AND… clearing the error flags has allowed the sessions to merge (even when timeouts are hit). So, at least in 1.5.3, "option 3" isn't working when a session is in an error state. However, by removing the e-mails on processing errors, we don't need it. 

Thanks,

Bennett