Closed 6293 closed 3 years ago
We are aware of that see this #17. Solution can be on Agent Start mainly using the initializer to set all dangling operation of a module (fragment) to FAILED with Failed Reasons "Operation was interrupted and could not be executed completely".
I will implement a proposal.
Solved & Pushed in main branch.
When an agent has accidentally shut down after it sent
501
(EXECUTING) and before502
/503
(failure / success), it creates a "dangling" operation in the Cumulocity server. After the device restart, this operation is not visible from the agent since the cloud will not resendEXECUTING
operations (they only resendPENDING
operations).Besides, if you create a new operation which has the same fragment as the dangling operation, the dangling operation would be set to
SUCCESS
and the new one is set toEXECUTING
. This is because the agent would successfully send501
then503
to the cloud, but503
will only update the old operation while501
is applied to the new one.