Best answer

"Find Data" not finding data for GitHub app

  • 13 March 2020
  • 3 replies
  • 108 views

Userlevel 2

I created a straightforward GitHub→Slack zap, but something is going wrong with the first (GitHub) step.

The “Find Data” operation worked once, when I set the zap up, but since then it hasn’t been able to retrieve any new issues. The “We're checking for a new issue in GitHub. Create a new issue in GitHub. We'll keep trying for 3 minutes.” notification shows up, but no new samples are returned.

The zap also doesn’t get triggered, though loads of issues are being created. Under “Customize Issue”, I’m filtering only on “Organization”.

Is anyone else experiencing similar issues with the GitHub app?

 

 

icon

Best answer by Danvers 17 March 2020, 17:31

View original

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

3 replies

Userlevel 7
Badge +12

Hi @Jean I’m sorry that you’re having trouble with your GitHub Zap, let’s see if we can get to the bottom of things!

 

For the sample, could I ask if any new issues have been added in the last 24 hours? And do you know if any have been assigned to you?

 

And when the Zap is on, are the issues added assigned to anyone?

Userlevel 2

Hi! Yes, issues are constantly being added, about 30 today.

Some are assigned, some aren’t. I don’t think any new ones have been assigned to me, but nothing in the zap refers to issue assignment or should depend on it.

Userlevel 7
Badge +12

Thanks for the clarification with this. I’m afraid that the problem is that the issues aren’t assigned to you (or the account connected to the Zap). We recently found a bug with the GitHub integration where if a user only specifies and Organization and no Repo in the trigger setup then the Zap will only trigger on issues assigned to the connected Github account. 

I've added you as an affected user on the issue report, which lets the team know how many users have been affected and also means that we will send you an email if we have an update on this.

If you only have a couple of repos, then the best thing to do would be to create separate Zaps for each repo. I appreciate that this isn’t a great solution and I’m sorry for the hassle while we look into the bug.