Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flows: results doubled for actions like log to console or email notification #13739

Closed
meditadvisors opened this issue Jun 5, 2022 · 5 comments · Fixed by #13783
Closed

Flows: results doubled for actions like log to console or email notification #13739

meditadvisors opened this issue Jun 5, 2022 · 5 comments · Fixed by #13783
Assignees
Labels

Comments

@meditadvisors
Copy link

Describe the Bug

The results of flows are doubled for actions like Log to console, Send email or notification.

To Reproduce

Create a test flow with an event hook on item added to log to console (or send email)

Note the double action/output... If email is configured you will get 2 emails.

Screen Shot 2022-06-05 at 17 55 29

Errors Shown

check the action log and notice same 2 actions/messages

What version of Directus are you using?

9.12.1

What version of Node.js are you using?

16.15.0

What database are you using?

does not matter, tested on both postgres and sqllite

What browser are you using?

does not matter

How are you deploying Directus?

Docker

@jsbrain

This comment was marked as duplicate.

@sfarrowGR

This comment was marked as duplicate.

@izoukhai

This comment was marked as duplicate.

@nickrum nickrum self-assigned this Jun 5, 2022
@emrahnazif
Copy link

emrahnazif commented Jun 8, 2022

For information:
@benhaynes This can be also related with cache isn't being properly cleared.
My issue is different #13780 but, after I restart the Directus. I feel like this is solved as well.

@nickrum
Copy link
Member

nickrum commented Jun 8, 2022

@emrahnazif I'm working on a fix that should hopefully fix both issues.

In the meantime, restarting Directus should also work as a workaround for this issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants