Analysis date is missing milliseconds

SonarQube Server / Community Build
1

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube Server v2026.1 )
  • how is SonarQube deployed: Docker
  • parallel builds with sample projects
  • nothing

The first build job in the same second was successful. The second one failed.

2026-06-12T08:51:56.4301751Z ##[warning]Error while executing SonarQube:Publish task: [SQ] Task failed with status FAILED, Error message: Validation of project failed:

  o Date of analysis cannot be older than the date of the last known analysis on this project. Value: "2026-06-12T08:51:49+0000". Latest analysis: "2026-06-12T08:51:49+0000". It's only possible to rebuild the past in a chronological order.

2026-06-12T08:51:56.4306766Z ##[error][SQ] Task failed with status FAILED, Error message: Validation of project failed:

  o Date of analysis cannot be older than the date of the last known analysis on this project. Value: "2026-06-12T08:51:49+0000". Latest analysis: "2026-06-12T08:51:49+0000". It's only possible to rebuild the past in a chronological order.
2

Hello @stephan.wolf and welcome to the Community! The “missing milliseconds” bit is not the cause of the issue. The server does register the millisecond mark from the analysis timestamp. The timestamps that you see in the error message are formatted for display and rounded to seconds.

What is happening in your case is most likely that analysis A is recording the timestamp slightly earlier than analysis B (this happens in the scanner/client/CI side), however analysis B reaches the server before analysis A. The server rejects analysis A because its timestamp is earlier than the timestamp of the last analysis it received (analysis B).

I would say your best bet is to simply not run analyses in parallel targeting the same branch/PR. Is there a particular reason why you’re doing it?

3

Hello Andrés,

You mean the timestamp is taken during the analyze step but the publish is a little bit too late, right?

Make sense to me.

For clarification: We are using yaml templates in Azure Devops for CI and CD Pipelines for different projects, but these projects are maintained by different users. So, we need to synchronize the sonar part in the template.

Thanks for your help,

Mit freundlichen Grüßen/ With kind regards

i. A. Stephan Wolf
Expert Software Developer

Mit freundlichen Grüßen/ With kind regards

i. A. Stephan Wolf
Expert Software Developer

Kontron AIS GmbH

Otto-Mohr-Straße 6
01237 Dresden, Germany

Tel. / Phone: +49 351 2166 1360
Mobile: +49 151 1455 3652

mailto:Stephan.Wolf@kontron-ais.com

Sitz der Gesellschaft: Dresden; Registergericht: Amtsgericht Dresden, HRB 26860; USt-ID: DE 263814591
Geschäftsführung: Dipl.-Ing. Dirk Sauer, Dipl. -Ing. Michael Jacob

Registered Office: Dresden; Register Court: Amtsgericht Dresden, Comm. Register 26860; VAT ID: DE 263814591
General Management: Dipl.-Ing. Dirk Sauer, Dipl. -Ing. Michael Jacob

Bitte beachten Sie unsere Datenschutzhinweise./Please take note of our data protection policy.

Wichtiger Hinweis: Beachten Sie bitte, dass jede Form der unautorisierten Nutzung, Veröffentlichung, Vervielfältigung oder Weitergabe des Inhalts dieser E-Mail nicht gestattet ist. Diese Nachricht ist ausschließlich für den bezeichneten Adressaten oder dessen Vertreter bestimmt. Sollten Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein, so bitten wir Sie, sich mit dem Absender der E-Mail in Verbindung zu setzen.

Important Note: Any form of unauthorised use, publication, reproduction, copying or disclosure of the content of this e-mail is not permitted. This message is exclusively for the person addressed or her/ his representative. If you are not the intended recipient of this message and its contents, please notify the sender immediately.

Please consider your environmental responsibility, before printing this e-mail. Ask yourself whether you need a hard copy!________________________________