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
We've recently uncovered some discrepancies in the re-claming process that are impacting parent nodes. Specifically, when a user attempts to reclaim a parent node, the operation is successful. However, subsequent to this action, in some cases, the parent node has problems properly adding any associated child nodes.
This issue is isolated and only affecting the reclaiming operation, the fist claiming operation is not affected.
In the last month we've identified 25 nodes affected, however, we're actively investigating the root cause and we will try to have a fix as soon as possible.
Expected behavior
parent should add child nodes properly after re-claiming.
Bug description
We've recently uncovered some discrepancies in the re-claming process that are impacting parent nodes. Specifically, when a user attempts to reclaim a parent node, the operation is successful. However, subsequent to this action, in some cases, the parent node has problems properly adding any associated child nodes.
This issue is isolated and only affecting the reclaiming operation, the fist claiming operation is not affected.
In the last month we've identified 25 nodes affected, however, we're actively investigating the root cause and we will try to have a fix as soon as possible.
Expected behavior
parent should add child nodes properly after re-claiming.
Steps to reproduce
re-claim a parent node
Screenshots
No response
Error Logs
No response
Desktop
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Browser Version [e.g. 22]
Additional context
No response
The text was updated successfully, but these errors were encountered: