If an Ibexa Migration failed for some reason while being executed with lock (by default), the next run fails with the following message:

[WARNING] Another migration process is still being executed. 

For a developer who uses it rarely there's not enough information about what to do and it takes some time to find it (or ask pawel.niedzielski@ibexa.co for help ). Maybe the message should be something like:

[WARNING] Another migration process is still being executed. Pass --disable-locking option to the command, to execute the migration regardless

or something similar (language help from Knowledge Team suggested)

I was also thinking that maybe we don't want to disable locking entirely, but rather overwrite previous stale result. So maybe instead we should have --force option?