3. Data Issue: we have implemented a fix to address the data errors in the “Places you’ve helped” section of the Monthly Contribution email. These issues should now be resolved for some editors.
4. Segments: fixed an issue where updating a node connection to point to a new node would fail if the original node was deleted in the same save stack leading to ‘Node was used after deleting the node’ error.
This place was removed from the map by me last month and it’s back on the map. I don’t know if it’s back now or if it was never deleted, and I don’t know if this happens with other places.
Hey Nataliia, would you please kindly pass this to Team!
Just wanted to share some feedback regarding the deprecation warnings in the current version. They’ve become quite verbose, which makes the logs a bit harder to parse during development.
I know the goal is to get everyone onto the latest SDK, but many scriptwriters haven’t been able to fully migrate yet due to various technical and resource constraints. Could we possibly tune these down or make them more concise in the next update? It would really help those of us still in the transition phase.
Thank you for flagging these issues. Could you please attach a permalink(s) for the suggestion (suggestions) you have problems with approving, which you mentioned?
@Nataliia_Staff Today, I encountered three instances where I was unable to approve the new suggestions due to an error message indicating that the change is not allowed at this time.
