[MAGNOLIA-1397] (to check) with the default activation workflow, it seems that the workitem is lost if the subscriber is not reachable Created: 22/Feb/07 Updated: 30/Nov/07 Resolved: 29/Nov/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | workflow |
| Affects Version/s: | 3.0.1 |
| Fix Version/s: | 3.5 RC2 |
| Type: | Bug | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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: |
| Comments |
| Comment by Boris Kraft [ 30/Nov/07 ] |
|
I think this could very well happen. IIRC the workflow calls the activation command, and activation will more or less silently fail if a subscriber is not reachable, right? So the workitem would be discarded after activation, even though the content is not activated. If it were the other way, i.e. activation command actually detects and informs WF that it can't activate, the WF could try reactivating at a later point in time until it succeeds, which would make activation more reliable (still no sync but closer) |