see issue
https://www.drupal.org/project/drupical/issues/3413851 →
as a reference.
We have to check why the node on drupical was not updated.
investigate first if there was an errror (node was nearly 2 years on d.o. not updated or check how we handle date/time, location, title etc updates in drupical backend.
if needed, implement an update process/step to avoid this problems in the future
none
none
none
Active
drupical.com service
This should be fixed with last changes we pushed to drupical backend, after fixing that -> accesCheck() issue in custom modules