You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: