Skip to main content
Solved

Smoke test - Failing without job started and spam the logs

  • February 20, 2026
  • 3 replies
  • 73 views

Ionut
Warrior
Forum|alt.badge.img+2

Hello!

We encountered a strange behavior (not sure what started it) on the smoke test part.

We don't have any job started in Jobs.

Basically we are spammed with logs that it is failing because 'Application id/alias' was not provided.

There are around 30 entries/second, do you have any idea what is happening and why?

Update: after a restart of web app it stopped, but anyway we need to find what was the issue.

Investigated a bit more and looks like we had it also before but we didn't saw it, so is not the first time.

Looks like the last time (10 feb & 11 feb) it was stopped somehow itself because it created max 500k records (without a restart from our side), not like this time.

Normally it was going up to 11k records max.

 

Best answer by Dani

Hey ​@Ionut,

We suspected that the branch might being archived while the test is running, but to know for sure we need to investigate it further.

Please create a ticket on TCP so we can investigate this issue further.

 

Kind regards,

Dani
 

3 replies

Ionut
Warrior
Forum|alt.badge.img+2
  • Author
  • Warrior
  • February 23, 2026

Update 2: tried in this morning to run the smoke tests, at first it didn't run (also no errors) and I aborted the job

At second try of the run, it was running, finished also successfully, but from the start and also after they were finished, it was spamming the same error in debug center, start & stop of the SF app didn't helped, just restart of the web app


Dani
Moderator
Forum|alt.badge.img+2
  • Moderator
  • Answer
  • February 23, 2026

Hey ​@Ionut,

We suspected that the branch might being archived while the test is running, but to know for sure we need to investigate it further.

Please create a ticket on TCP so we can investigate this issue further.

 

Kind regards,

Dani
 


Ionut
Warrior
Forum|alt.badge.img+2
  • Author
  • Warrior
  • February 23, 2026

Hey ​@Ionut,

We suspected that the branch might being archived while the test is running, but to know for sure we need to investigate it further.

Please create a ticket on TCP so we can investigate this issue further.

 

Kind regards,

Dani
 

Ok, will create one. Thanks!