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

Flow: fail to pick a third party entity event #18510

Closed
blizzz opened this issue Dec 20, 2019 · 0 comments · Fixed by #18547
Closed

Flow: fail to pick a third party entity event #18510

blizzz opened this issue Dec 20, 2019 · 0 comments · Fixed by #18547
Assignees
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap bug feature: workflows

Comments

@blizzz
Copy link
Member

blizzz commented Dec 20, 2019

Can be tried with otherwise incomplete https://github.com/blizzz/flow_http_requests

  1. Have spreed master running
  2. Have flow_http_requests enabled (or anything else that registers a new entity)
  3. Go to personal flow settings
  4. start a "Write to conversation" flow
  5. Try to pick "Web request" (or your event)

The expected check mark does not show up, and the event is not written to the list. Only selecting the files related events is functioning.

@juliushaertl

@blizzz blizzz added bug 0. Needs triage Pending check for reproducibility or if it fits our roadmap feature: workflows labels Dec 20, 2019
@blizzz blizzz added this to the Nextcloud 18 milestone Dec 20, 2019
@juliusknorr juliusknorr self-assigned this Dec 23, 2019
juliusknorr added a commit that referenced this issue Dec 23, 2019
juliusknorr added a commit that referenced this issue Dec 23, 2019
juliusknorr added a commit that referenced this issue Dec 23, 2019
juliusknorr added a commit that referenced this issue Dec 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap bug feature: workflows
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants