Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

New State type: TRIGGER_FAILED

See original GitHub issue

When a task fails, and the following task also fails because it has an all_successful trigger, it would be helpful to know that the second task didn’t fail because of an error or execution problem, but that it failed because the upstream task failed.

We’ve discussed creating an UPSTREAM_FAILED state to represent this behavior, but it could create odd situations: supposing a task has an all_failed trigger and the upstream task succeeds. Should the resulting task really say UPSTREAM_FAILED?

I think we need a TRIGGER_FAILED which might act functionally like a SKIP but not be treated as a SUCCESS.

Issue Analytics

State:
Created 5 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

jlowincommented, Jul 18, 2018

I’m on board with TriggerFailed subclassing Failed – one of the reasons I was hesitant about that at first was it would then trigger subsequent tasks as if the task had failed (for example, if the subsequent task had an all_failed trigger) but your skip analogy helps me see that that is probably a good thing

0reactions

cicdwcommented, Jul 18, 2018

Closed with #59

Top Results From Across the Web

"Configuring the trigger failed, edit and save the pipeline ...

The pipelines run perfectly fine, however I get a "Some recent issues detected related to pipeline trigger." warning at the top of the...

Troubleshoot common issues with triggers - Power Automate

This error means that Power Automate tried multiple times to establish a connection to register the trigger and failed.

New Writeup for ASE Error Message 2116 - SAP Blogs

Msg: 2116, Level: 16, State: 1 CREATE TRIGGER failed because selecting from a TEXT, IMAGE, UNITEXT or off-row Java datatype column of the ......

googleapi: Error 409: trigger already exists · Issue #370 ...

When attempting to update a CloudBuildTrigger, by kubectl apply or edit to change a step, the apply succeeds but then KCC reverts the...

ORA-04098: trigger is invalid and failed re-validation tips

Cause: A trigger was attempted to be retrieved for execution and was found to be invalid. This also means that compilation/authorization failed for...