Hi Jonas
This is a typically unsync counter. You can see the error in php_error.log with:
tail -f ../dedalo_home/logs/php_error.log
And you will see that error as something like:
[type] => 2
[message] => pg_query_params(): Query failed: ERROR: duplicate key value violates unique constraint "matrix_hierarchy_section_id_section_tipo_key"
DETAIL: Key (section_id, section_tipo)=(42, object1) already exists.
That is saying that the new record is behind the last counter number, therefore it is not possible to create a new record with this section_id, in this case 42, because the counter has the highest number. The unsync can occur if you are importing, deleting, or rebuilding, etc. the sections manually, and this situation needs to be controlled, because if you want to sustain the Time Machine, the section_id needs to be preserved. For example:
You create 50 register from 1 to 50
You remove the last 20, from 30 to 50
Time Machine will store that 20 delete registers.
BUT, if you uncheck the Time Machine in the import tool, these records will NOT be controlled by Time Machine, but the counter has to be set to 50, but you only have 30. When you try to create a new one with the 31, it conflicts with the previous section_id, because the counter has to be set to 30, and the error appears.
So, in those cases, you need to fix the counter. Go to the Maintenance panel and locate the DEDALO COUNTER STATUS panel.
Locate the section_tipo that has the error. You will see that the counter value and last section_id are unsync in this way:
Counter value < Last section_id
If you see that, click the Fix counter button; it will set the counter correctly.
Important note:
If you see
Counter value > Last section_id
That's correct, because the counter is higher than the last section_id, so the next one will not conflict with previous records, so the gap is for deleted records that are stored in Time Machine. So, DON'T fix those counters.
I hope this is clear.
Best
