Daniel

Hi Andreas, sorry was absent, so I could not respond. Great that you found it anyway. :-) Best regards, Daniel

Hi Andreas, sorry for not sharing all details. We have JS7 2.8.3 here. What I have done: Tried to remove the old workflow from the journal. According to the command, it was gone then. Tried to remove the agent from the journal. According to the command, it was gone then. Tried to remove the agent through JOC, but it was still reported to be linked to the workflow. Then I have seen controller log messages, telling me that the journal is corrupt (JSON sequence read from 'controller--1777883772685003.journal'...

Hello again, unfortunately, I seem to be affected by the same issue described here: https://github.com/sos-berlin/js7/issues/14 Any hints? Something that's not in the docs yet? Best regards Daniel

Hi Andreas, thank you for your fast response! I've dropped the whole workflow (where it was once used), also in the recycle bin. I've started a new agent and pointed the existing record to the new host, so it seems to be "up" again. But: I still cannot delete the agent as it is still referenced in the old (but deleted) workflow. I have tried to remove the workflow from the controller's journal as described in the link you mentioned, but it did not help (it vanished from the commands output, but then...

Hi Andreas, thank you for your fast response! I've dropped the whole workflow (where it was once used), also in the recycle bin. I've started a new agent and pointed the existing record to the new host, so it seems to be "up" again. But: I still cannot delete the agent as it is still referenced in the old (but deleted) workflow. I have tried to remove the workflow from the controller's journal as described in the link you mentioned, but it did not help (it vanished from the commands output, but then...

Dear all, I have to remove an agent as the complete host was removed. I am able to disable the agent - but cannot remove it: The error message tells me that it is still referenced in a workflow. Indeed, there was once a job in the mentioned workflow but that job is already gone since two weeks. Could it be that JS7 finds this reference in the workflow's version history? If so, how can I wipe all dangling references to this agent? Best regards Daniel

Dear all, first of all, not to forget: Great work. :-) After upgrading to 2.8.3 we have a strange effect in the "Workflows" view: We had workflows X, Y in a folder like /TeamA/ some time ago and moved them to a new structure /teams/TeamA. In the meanwhile we have also added a workflow Z in the new folder. That is also what we see in the Inventory view. But, in the Workflows view, I do not see only /teams/TeamA/[X|Y|Z] - but I see them also in the former folder /TeamA, but only the older workflows...

Hi Andreas, Well, the affected workflow was scheduled to run in the morning at 2am. It finished at 2:18am successfully. No other executions are planned for today. The release of the calendar happend at around 10am and the workflow started again. Can you give me some other hints how to track down what happened here?