xzyJavaX opened a new issue, #9742: URL: https://github.com/apache/skywalking/issues/9742
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no similar issues. ### Apache SkyWalking Component OAP server (apache/skywalking) ### What happened During the creation of profiling task, a field called time_bucket will be generated,time_bucket is converted from the end time of task monitoring.For example, for Task A, the monitoring start time is 12:00:00, the monitoring time is 5 minutes, and the monitoring end time is 12:05:00, time_bucket is 12:05.Then create Task B, with the start time of 12:04:00 and the end time of 12:09:00, will go to the database to check whether there is a time_ Buckets in this range. If yes, throw "current service already has monitor task execute at this time".For example, start is 12:04:00, end is 12.09:00, and there is a time_bucket is 12:05, so Task B failed to be created. But if you create a task with a monitoring time of 15 minutes at 12:00:00, time_bucket is 12:15. At this time, a task with start is 12:04:00 and end is 12:09:00 can be created successfully. This should not be as expected. There is also a UI problem. When the "current service already has monitor task execute at this time" is returned, the pop-up window will show that the creation was successful, but it was not actually created.  ### What you expected to happen In this case, profiling tasks should not be created ### How to reproduce First create a profiling task with a monitoring duration of 15 minutes, and then create a profiling task with a monitoring duration of 5 minutes ### Anything else _No response_ ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
