v_ Sync Queue Action Log

A view that will be used as a collection on SyncQueue panel to show the actions that have been executed to complete the sync process.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
int32

The SyncQueueId is an essential field in the SyncQueueActionLog table, which stores a log of actions related to synchronization queue. It is of data type int, and it serves as a unique identifier for each entry in the table. This field is crucial in tracking and managing the synchronization process, as it helps in identifying which action was taken on which item in the queue. The SyncQueueId is automatically assigned to each action log entry and can be used as a reference for troubleshooting and debugging purposes. It also enables the system to maintain a chronological order of actions in the synchronization queue, ensuring efficient and smooth synchronization between data sources.

int32

The ActionLogId field in the SyncQueueActionLog table is a data type of integer that serves as a unique identifier for each action log entry. This field is used to track the actions performed in the synchronization queue, providing a detailed record of the tasks completed or any errors encountered during the synchronization process. It allows for easy referencing and organization of the action logs for troubleshooting and auditing purposes. The values of this field are auto-generated and cannot be modified, ensuring accuracy and consistency of the recorded data.

date-time
required

The Started field in the SyncQueueActionLog table is a datetime2 data type that tracks the date and time at which a synchronization action was started. This field is useful for monitoring the performance of the synchronization process and identifying any potential issues that may have occurred during a specific synchronization session. The datetime2 data type allows for precise and accurate timestamping, making it a reliable tool for tracking the start time of a synchronization action. Along with other relevant fields in the SyncQueueActionLog table, the Started field helps provide a comprehensive overview of the synchronization process and aids in troubleshooting and optimization efforts.

date-time
required

The Ended field in the SyncQueueActionLog table is a datetime2 data type that tracks the date and time at which an action was completed in the synchronization queue. This field is valuable for recording the duration of synchronization processes, as well as identifying any errors or delays that may have occurred. By storing this data, the Ended field allows for easy analysis and troubleshooting of synchronization activities, providing valuable insights for optimizing system performance and ensuring accurate data synchronization.

int32 | null

The Duration field in the SyncQueueActionLog table is an integer data type that represents the length of time it takes for each action to complete in the synchronization queue. This data is important for monitoring the efficiency of the synchronization process and identifying any potential bottlenecks. The values in this field are measured in milliseconds and can provide valuable insights into the performance of the system. By tracking the duration of each action, administrators can make informed decisions about optimizing the synchronization process to improve overall system functionality.

int32

The Status field in the SyncQueueActionLog table is of data type int and is used to track the current status of a data synchronization process. This field indicates whether the synchronization was successful, incomplete, or encountered an error. It serves as a valuable tool for monitoring and troubleshooting data synchronization issues in various systems. With a range of numeric values, the Status field provides a detailed view of the progress and outcome of each synchronization action in the SyncQueueActionLog table. This information can aid in identifying and resolving any data discrepancies, ensuring the accuracy and reliability of synchronized data.

string | null

The ActionExecutionStateId field in the SyncQueueActionLog table is a primary key field that stores a unique identifier for each action execution state. The data type for this field is nvarchar with a maximum length of 450, allowing for a wide range of characters to be stored. This field serves as a key for accessing and tracking the current state of actions within the SyncQueue. By utilizing a primary key, this field ensures efficient retrieval and manipulation of data in the SyncQueueActionLog table.

string | null

The field 'Message' in the 'SyncQueueActionLog' table is of data type nvarchar and serves as a storage space for textual information associated with the synchronization queue actions. This field can contain a variety of data such as error messages, success messages, and other relevant details that can help track and troubleshoot synchronization activities. It provides a comprehensive record of the actions taken on the synchronization queue, aiding in the efficient management and monitoring of data synchronization processes.

string | null

The Result field in the SyncQueueActionLog table is a form of data storage that is defined by the nvarchar data type. This field is a method for storing text-based results of actions that have been synchronously initiated and recorded in the SyncQueueActionLog table. The nvarchar data type allows for a maximum length of characters to be stored, making it suitable for a wide variety of potential results. The data stored in this field can provide valuable insights into the success or failure of important actions taken within the synchronized queue system. It serves as a record of the outcome of each queued action, providing meaningful and informative data for analysis and troubleshooting purposes.

Headers
string
enum
Defaults to application/json;odata.metadata=minimal;odata.streaming=true

Generated from available request content types

Response
200

OK

Language
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here!