Cancelled Tasks assign themselves?

[TomMack 28]

Hey guys,

 

When I cancel a task that has not been assigned, the cancel notification shows as expected but the next notification is that the task has been "assigned". 

Despite the notification saying the task was assigned, it remains cancelled when you check it in the Diary.

Is there a reason for this?

 

Thanks.
p.s. I'll upload a video if that makes it any easier to understand.

[TomMack 28]

The task is created with this code:

Quote

[west,["mck_inv1"],["Investigate the new Firing Range.","Firing Range"],MCK_rangeMaster,"CREATED",2,true,"search"] call BIS_fnc_taskCreate;

 

The task is cancelled with this code:

Quote

[west,["mck_inv1"],["Investigate the new Firing Range.","Firing Range"],MCK_rangeMaster,"CANCELED",2,true,"search"] call BIS_fnc_taskCreate;

 

Any Ideas?

[mrcurry 508]

54 minutes ago, TomMack said:

The task is created with this code:

 

The task is cancelled with this code:

 

Any Ideas?

Try cancel it with BIS_fnc_taskSetState instead. 

 

["mck_inv1", "Canceled" ] call BIS_fnc_taskSetState

 

 

[TomMack 28]

53 minutes ago, mrcurry said:

Try cancel it with BIS_fnc_taskSetState instead. 

 

["mck_inv1", "Canceled" ] call BIS_fnc_taskSetState

Thanks for the response.

 

I have sorted now... I was calling the already assigned task as succeeded before cancelling the other task. The reason it showed as assigned was because the notification was queued from that task being the next in line to be assigned.