[EXCONTRANS-308] Getting a submission stuck "blocks" future submissions Created: 08/Nov/18 Updated: 25/Feb/20 Resolved: 25/Feb/20 |
|
| Status: | Resolved |
| Project: | Content Translation Extended (CTX) |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Sascha Oberhuber | Assignee: | Teresa Miyar |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 1h | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Magnolia 5.6.X |
||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
Hi all, this one is the little brother to I used a copy of the page referenced in that ticket to create another batch, this time including subnodes. The resulting batch is created fine under Translation Batches, but I'm unable to submit it, as "Submit Batch" is greyed out in the app. Edit batch, Delete batch, Get history, and Export are available. The batch's status remains OPEN. Attachments:
As always, if more information is needed, hit me up. |
| Comments |
| Comment by Trung Luu [ 08/Nov/18 ] |
|
Hi soberhuber, This issue might be caused by the 'IsMultiSubmissionAvailabilityRule' of translation batches app definition. Somehow the Best regards, |
| Comment by Sascha Oberhuber [ 08/Nov/18 ] |
|
Deleting the property allowed me to submit again, thanks for the help. Is there a more "canonical" solution to do this? How high is the risk of me breaking things if I remove the rule from the app definition? In production, it's not unheard of for us to have multiple batches submitted in parallel, as we may partition our content depending on priorities. Regardless, I guess that solves the "bug" and may just become a suggestion for improvement. Regards |
| Comment by Sascha Oberhuber [ 08/Nov/18 ] |
|
Ignore that. I realized that the property auto-deletes once the actual submission is done, so that's perfectly fine in my book. So the only real issue is that getting a submission stuck "blocks" future submissions. |
| Comment by Trung Luu [ 09/Nov/18 ] |
|
Thanks for update. We will keep you posted in |
| Comment by Teresa Miyar [ 17/Dec/19 ] |
|
Changed title since the issue to follow up here is the one in the 08/Nov/18 comment |