24
Views
7
Comments
Solved
[Trigger Pipeline] Pipeline isn't automatically triggered after a new version tag
trigger-pipeline
Web icon
Forge asset by OutSystems Lab
Application Type
Traditional Web

Hello!
I can trigger the pipeline manually (and select which version I want to use) or via timer without any errors.

But, when I tag a new version of the same app nothing happens.

Also the pipeline dashboard shows me the first version of the app and not the latest.

Can you help?


Thanks,

Diogo

2019-03-18 15-58-58
Duarte Castaño
Staff
Solution

Hi Diogo,

Triggering the pipelines automatically whenever there are new app versions is done via the  'CheckNewVersionsForPipeline' timer.
This timer needs to be configured to run on a schedule, and the minimum configuration is to run every 5 minutes.

Do you have a schedule defined for this timer?

Cheers,
Duarte Castaño

2025-10-04 16-11-01
Diogo Mendes

ah , got it. I thought we could trigger the pipeline whenever we clicked "tag version". But in reality the timer will always be required because, he is the one doing the checks.

got it, thanks for the help Duarte!

Let's see if you see my name with another question in the near future or not! :D thaanks!

2023-05-16 02-25-49
Xiao Hui

You are not alone, I am also facing the same issue, yet to get any solution.

https://www.outsystems.com/forums/discussion/99400/trigger-pipeline-checknewversionsforpipeline-timer-not-able-to-trigger-the-pipe/

2025-10-04 16-11-01
Diogo Mendes

Hello! But we have different problems, regarding the timer not running please check your integration endpoints, and check that on everything except PropertiesAPI and LifeTimeAPI you have you OWN environment as an endpoint.

Also make sure to flag your pipeline to be triggered on schedule.

Also configure the service account with the correct permissions on lifetime and change the site property value -> the same for the environment key.

Try these and let me know.

2019-03-18 15-58-58
Duarte Castaño
Staff

Hi @Diogo Mendes and @Xiao Hui,

The triggers may have different behaviors depending on the features enabled via site properties.
Can you share what the value is for them?

Could you also elaborate more on the issue? When you get into the trigger manifest screen does it show the correct app version? When you say nothing happens, after a manual tag, do you mean the timer does not trigger the pipeline it is supposed to?

Regards,
Duarte Castaño

2025-10-04 16-11-01
Diogo Mendes

Hello @Duarte Castaño ,

Manifest view:

Site Properties:


Endpoints:

Manually trigger:

I can trigger the github pipeline via Manual Triggering on the Trigger pipeline dashboard and via manually clicking on "CheckNewVersions" timer on service center, on the trigger pipeline module.

What I want to achieve is this:

Thank you

2023-05-16 02-25-49
Xiao Hui

I have already rolling back to old version. I decided not to upgrade for now since I was not able to resolve the issue for months. 

Probably will plan for update if there is new version.

2019-03-18 15-58-58
Duarte Castaño
Staff
Solution

Hi Diogo,

Triggering the pipelines automatically whenever there are new app versions is done via the  'CheckNewVersionsForPipeline' timer.
This timer needs to be configured to run on a schedule, and the minimum configuration is to run every 5 minutes.

Do you have a schedule defined for this timer?

Cheers,
Duarte Castaño

2025-10-04 16-11-01
Diogo Mendes

ah , got it. I thought we could trigger the pipeline whenever we clicked "tag version". But in reality the timer will always be required because, he is the one doing the checks.

got it, thanks for the help Duarte!

Let's see if you see my name with another question in the near future or not! :D thaanks!

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.