On this page

Show all

Help Center/ Cloud Trace Service/ FAQs/ Why Is an Operation Recorded Twice in the Trace List?

Why Is an Operation Recorded Twice in the Trace List?

Updated on 2022-09-27 GMT+08:00

View PDF

For an asynchronously invoked trace, such as deleteDesktop trace of Workspace, two records with the same trace name, resource type, and resource name will be generated. The two records may seem to be the same. However, they are generated at different times and document different details.

The first record documents the request initiated by a user.
The second record documents the response to the request and the operation result, and is usually several minutes later than the first record.

The two records together give a full view of the operation.

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel