Task Persistence database event states

Document ID : KB000025728
Last Modified Date : 11/07/2018
Show Technical Document Details
Introduction:

 Question:

 What are the different event statuses available in Task Persistence Database?

 

Answer: 

This is the list of task states:

BEGIN_STATE = 0x00; // 0
PRE_STATE = 0x01; // 1
INVALID_STATE = 0x02; // 2
PENDING_STATE = 0x04; // 4
EXECUTING_STATE = 0x08; // 8
APPROVED_STATE = 0x10; // 16
REJECTED_STATE = 0x20; // 32
POST_STATE = 0x40; // 64
COMPLETED_STATE = 0x80; // 128
CANCELLED_STATE = 0x100; // 256
MARK_FOR_DELETION_STATE = 0x200; // 512
UNKNOWN_STATE = 0x300; // 768
INITIAL_STATE = 0x400; // 1024
PRIMARY_PENDING_STATE = 0x800; // 2048
PRIMARY_COMPLETE_STATE = 0x1000; // 4096
SECONDARY_PENDING_STATE = 0x2000; // 8192
AUDIT_STATE = 0x4000; // 16384

SCHEDULED_STATE = 0x8000;// 32768
PRE_TASKS_PENDING_STATE = 0x10000; // 65536
PRE_TASKS_COMPLETE_STATE = 0x20000; // 131072
POST_TASKS_PENDING_STATE = 0x40000; // 262144
POST_TASKS_COMPLETE_STATE = 0x80000; // 524288
TASK_ABORTED_STATE = 0x100000; // 1048576

Offline endpoints related states:
PARTIAL_COMPLETE_STATE = 0x140000; //1310720
RESUBMITTING_STATE = 0x200000; //2097152

All the task states are mapped to 'pending' and 'in progress' except for 'completed', 'cancelled' and 'rejected'.

I.e., "In Progress" or "Pending" = TP states 0, 1, 2, 4, 8, 16, 64.

'Failed' tasks do not have a unique state because the tasks can fail during different events within the task. Failed tasks will have the last logged state at the time of the failure which could be one of the pending or in process states.

Instructions:
Please Update This Required Field