You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there is an error in your sequence submission, SNEx 2 does not tell you and there isn't really a way to trace the request, this is especially true for something that is submitted with a delay - so is shouldn't show up in the portal immediately.
@crpellegrino and I discussed this on Slack and this is what he had to say:
It's not trivial, those errors get written from the scheduling script into the snex1 database, so displaying them in snex2 would probably require mirroring that table into the snex2 database as well. this wasn't something I added at first because the idea was to eventually move on from using the snex1 scheduling script, but that just hasn't happened. In response to whether it would be possible to put this info in the database he responded: The easiest way to do that would probably be to modify the scheduling script itself, but i'm not sure how straightforward it is to have it write to the snex2 db
The text was updated successfully, but these errors were encountered:
If there is an error in your sequence submission, SNEx 2 does not tell you and there isn't really a way to trace the request, this is especially true for something that is submitted with a delay - so is shouldn't show up in the portal immediately.
@crpellegrino and I discussed this on Slack and this is what he had to say:
It's not trivial, those errors get written from the scheduling script into the snex1 database, so displaying them in snex2 would probably require mirroring that table into the snex2 database as well. this wasn't something I added at first because the idea was to eventually move on from using the snex1 scheduling script, but that just hasn't happened. In response to whether it would be possible to put this info in the database he responded: The easiest way to do that would probably be to modify the scheduling script itself, but i'm not sure how straightforward it is to have it write to the snex2 db
The text was updated successfully, but these errors were encountered: