I'm getting started with the Device Management Portal and I've started and stopped a few update campaigns, and deleted them afterwards, all without any problem.
However, I've now tried once more to create an update campaign but this time it always fails to start with the message "Active campaign already exists", even though there are no other active campaigns. In fact, this is the only campaign present.
The behaviour is actually identical to this forum post from a few months ago: https://forums.mbed.com/t/update-campaign-stop/8366
Will my account need some sort of recovery process as suggested in that forum post?
Hi, Can you provide more details on what sequence of steps you did before the campaign state, any errors/messages and also your account name or ID. Thanks
Hi, my account name (from arm mbed.os) is pcameli
The sequence of steps from IDE mbed: "Apply Update Certificate" + "Publish Firmware Update" + Start Campaign (from Pelion IDE)
[MAIN] Account ID: 016a73d9c28262cce657fffc00000000
[MAIN] Endpoint name: 0174d94043b300000000000100176b7a
[MAIN] Device ID: 0174d94043b300000000000100176b7a
Sorry for long delay again. Do you still have this issue? If so we might have to delete and release the device.
So far the important thing is to first stop the campaign before delete the campaign.