8000 Deleted workflow still attempting to run · Issue #48185 · keycloak/keycloak · GitHub
[go: up one dir, main page]

Skip to content

Deleted workflow still attempting to run #48185

Closed

Description

@leannebriffa

Before reporting an issue

  • I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.

Area

workflows

Describe the bug

After testing the Tracking of user activity and taking actions workflow in the documentation which creates a scheduled task, this workflow was deleted from the UI before being explicitly disabled.

After deletion, server logs show that the scheduled task associated with the workflow continues to execute and fails because the referenced workflow no longer exists:

ERROR [org.keycloak.services.scheduled.ScheduledTaskRunner] (Timer-0) Failed to run scheduled task workflow-032b10ae-dfc2-41be-996a-d3dc0e868282: jakarta.ws.rs.BadRequestException: Not a valid workflow resource: 032b10ae-dfc2-41be-996a-d3dc0e868282

This results in repeated error logs from ScheduledTaskRunner.

Version

26.6.0

Regression

  • The issue is a regression

Expected behavior

Deleting a workflow should also unregister or cancel any associated scheduled tasks, or prevent further execution attempts.

Actual behavior

The scheduled task continues to run and attempts to execute a workflow that has been deleted, resulting in repeated errors.

How to Reproduce?

Create a workflow as in the example in the documentation, delete without disabling and observe the logs.

Anything else?

No response

Activity

  1. added theissue type on Apr 17, 2026
  2. changed the title [-]Deleted scheduled workflow still attempting to run[/-] [+]Deleted workflow still attempting to run[/+] on Apr 17, 2026
  3. OrenKaizer1 commented on Apr 19, 2026

    @OrenKaizer1

    I experience this issue too.

  4. self-assigned this
    on Apr 20, 2026
  5. sguilhen commented on Apr 20, 2026

    @sguilhen
    Contributor

    @leannebriffa @OrenKaizer1 are you running the feature on a single node or on a cluster? I can see a possible issue with a cluster setup where the timer doesn't get properly deactivated on every node.

  6. leannebriffa commented on Apr 20, 2026

    @leannebriffa
    Author

    @sguilhen on a cluster. However already tried temporarily scaling down to a single node as suspected that this may be the case

  7. 15 remaining items

  8. added a commit that references this issue on Apr 27, 2026
    41ff67b
  9. OrenKaizer1 commented on Apr 28, 2026

    @OrenKaizer1

    What is the current status of the issue, was it solved?

  10. sguilhen commented on Apr 28, 2026

    @sguilhen
    Contributor

    @OrenKaizer1 Yes and the fix was backported to 26.6 branch, so the next release will have it.

  11. added a commit that references this issue on Jul 20, 2026
    28d47e8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Fields

No fields configured for bug.

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    0