[GH-ISSUE #1104] The workflow still stops after failing to run one nodes, even though there is no “End” node there #745

New issue

Closed

opened 2026-03-03 01:05:41 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 01:05:41 +03:00

Owner

Originally created by @FarrelF on GitHub (Dec 15, 2025).
Original GitHub issue: https://github.com/certimate-go/certimate/issues/1104

Release Version / 软件版本

v0.4.9

Description / 问题描述

I have a simple workflow like this:

As you can see that there is no "End" node after "Sent Notification to Telegram" and there is a monitoring node before 'End' node in the workflow, so I expect that after sent notification because node failure (e.g. certificate issuance failure in this case), the workflow still continue to running (e.g. run the monitoring node in this case), unless it ends using 'End' node.

But what actually happened was that the workflow stopped after sending the notification, even though there was no “End” node and the monitoring node was not running properly. The following is the screenshot:

Is there something wrong with this workflow? I have checked this several times before, but it seems that there is nothing wrong with the workflow.

So I think this is a bug in Certimate itself, or maybe I am wrong?

Miscellaneous / 其他

There is what I'm using

CPU: Intel Core i3-12100F (4 core, 8 thread)
Memory: 8x2 GB (16 GB) DDR4 Dual-Channel
OS: Windows 11 Pro 25H2 (26200.7462)
I'm running Certimate with native binary in Windows

The following is the workflow code that I export it to YAML format:

nodes:
  - id: "UwnoAwfuTKx-yV_I5Q1y1"
    type: "start"
    name: "Start"
    config:
      trigger: "scheduled"
      triggerCron: "*/5 * * * *"
  - id: "jwM3vdGjaHod5m8UDHsfh"
    type: "tryCatch"
    name: "Try to ..."
    blocks:
      - id: "jLEDW3wyMt3m4Lf6ckRs"
        type: "tryBlock"
        name: ""
        blocks:
          - id: "YGtxRr_LvPrhqFrXfIHgh"
            type: "bizApply"
            name: "Issue a Actalis Certificate"
            config:
              caProvider: "actalisssl"
              caProviderAccessId: "jr2x6zr8uzc2p8w"
              challengeType: "dns-01"
              contactEmail: "farrel@franqois.id"
              dnsPropagationWait: "60"
              dnsTTL: "60"
              domains: "farrelf.blog;www.farrelf.blog;example.farrelf.blog;example2.farrelf.b\
                log"
              keyAlgorithm: "RSA4096"
              keySource: "auto"
              provider: "bunny"
              providerAccessId: "937a849d05sten1"
              skipBeforeExpiryDays: 30
      - id: "AZU8ty6G42XNQ66QF3gTk"
        type: "catchBlock"
        name: "On failed ..."
        blocks:
          - id: "3szAtweYsImj2IkzqTa52"
            type: "bizNotify"
            name: "Sent Notification to Telegram"
            config:
              message: "Your certificate issuance by Actalis at \"{{ $workflow.name }}\"
                workflow on node \"{{ $error.nodeName }}\" has been failed.
                Please check the details.


                Error Message: {{ $error.message }}

                Node ID: {{ $error.nodeId }}

                Workflow ID: {{ $workflow.id }}

                Workflow Run ID: {{ $run.id }}

                Time: {{ $now }}"
              provider: "telegrambot"
              providerAccessId: "r290x117o17v176"
              providerConfig: {}
              subject: "[Certimate] Certificate Issuance Failure Alert!"
  - id: "64ekw3OLsG6s3aXWayF1"
    type: "bizMonitor"
    name: "Monitoring"
    config:
      host: "farrelf.blog"
      port: 443
      requestPath: "/"
  - id: "5sD-NCaUooFUZnE7XCTTC"
    type: "end"
    name: "End"

Originally created by @FarrelF on GitHub (Dec 15, 2025). Original GitHub issue: https://github.com/certimate-go/certimate/issues/1104 ### Release Version / 软件版本 v0.4.9 ### Description / 问题描述 I have a simple workflow like this: <img width="974" height="736" alt="Image" src="https://github.com/user-attachments/assets/33c6dde4-f717-4b55-9cbe-e53f3b3326f0" /> As you can see that there is no "End" node after "Sent Notification to Telegram" and there is a monitoring node before 'End' node in the workflow, so I expect that after sent notification because node failure (e.g. certificate issuance failure in this case), the workflow still continue to running (e.g. run the monitoring node in this case), unless it ends using 'End' node. But what actually happened was that the workflow stopped after sending the notification, even though there was no “End” node and the monitoring node was not running properly. The following is the screenshot: <img width="717" height="915" alt="Image" src="https://github.com/user-attachments/assets/f7bdd27b-bdfa-4f83-b606-d693bc140b63" /> Is there something wrong with this workflow? I have checked this several times before, but it seems that there is nothing wrong with the workflow. So I think this is a bug in Certimate itself, or maybe I am wrong? ### Miscellaneous / 其他 There is what I'm using - CPU: Intel Core i3-12100F (4 core, 8 thread) - Memory: 8x2 GB (16 GB) DDR4 Dual-Channel - OS: Windows 11 Pro 25H2 (26200.7462) - I'm running Certimate with native binary in Windows The following is the workflow code that I export it to YAML format: ```yaml nodes: - id: "UwnoAwfuTKx-yV_I5Q1y1" type: "start" name: "Start" config: trigger: "scheduled" triggerCron: "*/5 * * * *" - id: "jwM3vdGjaHod5m8UDHsfh" type: "tryCatch" name: "Try to ..." blocks: - id: "jLEDW3wyMt3m4Lf6ckRs" type: "tryBlock" name: "" blocks: - id: "YGtxRr_LvPrhqFrXfIHgh" type: "bizApply" name: "Issue a Actalis Certificate" config: caProvider: "actalisssl" caProviderAccessId: "jr2x6zr8uzc2p8w" challengeType: "dns-01" contactEmail: "farrel@franqois.id" dnsPropagationWait: "60" dnsTTL: "60" domains: "farrelf.blog;www.farrelf.blog;example.farrelf.blog;example2.farrelf.b\ log" keyAlgorithm: "RSA4096" keySource: "auto" provider: "bunny" providerAccessId: "937a849d05sten1" skipBeforeExpiryDays: 30 - id: "AZU8ty6G42XNQ66QF3gTk" type: "catchBlock" name: "On failed ..." blocks: - id: "3szAtweYsImj2IkzqTa52" type: "bizNotify" name: "Sent Notification to Telegram" config: message: "Your certificate issuance by Actalis at \"{{ $workflow.name }}\" workflow on node \"{{ $error.nodeName }}\" has been failed. Please check the details. Error Message: {{ $error.message }} Node ID: {{ $error.nodeId }} Workflow ID: {{ $workflow.id }} Workflow Run ID: {{ $run.id }} Time: {{ $now }}" provider: "telegrambot" providerAccessId: "r290x117o17v176" providerConfig: {} subject: "[Certimate] Certificate Issuance Failure Alert!" - id: "64ekw3OLsG6s3aXWayF1" type: "bizMonitor" name: "Monitoring" config: host: "farrelf.blog" port: 443 requestPath: "/" - id: "5sD-NCaUooFUZnE7XCTTC" type: "end" name: "End" ```