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

Reports show success when failure due to too many future calls. #3

Open
chexxor opened this issue Oct 23, 2012 · 0 comments
Open

Reports show success when failure due to too many future calls. #3

chexxor opened this issue Oct 23, 2012 · 0 comments

Comments

@chexxor
Copy link

chexxor commented Oct 23, 2012

This is both an issue report and a warning/pitfall to future users.

We were having problems with none of our scheduled reports being delivered successfully, even though the history shows it was successful.

After much investigation, we discovered that too many future calls were being used at one time. This is caused by scheduled too many to be sent at the same time, which causes them all to fail, I believe.

Anyways, the solution is to space them out. Send 10 at 5am, 10 at 6am, 10 at 7am. I believe the limit on future calls is spawning 20 in the same transaction, which voids the transaction.

This seems to be solvable, we just can't find time to design a fix and implement it.

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

No branches or pull requests

1 participant