-
Notifications
You must be signed in to change notification settings - Fork 52
Submissions not synced from v4 to v5 #195
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
Comments
@lakshmiathreya I believe this is fixed in the latest sync. Please close this out if so |
@rootelement , submissions get migrated to v5 when the migration script is run, but not in real time. What is the expected behaviour here? Is there a real time (1-5 mins lag) sync enabled for submissions made in v4 to be carried over to v5? |
@lakshmiathreya , @rootelement @mtwomey , this sync issue should not be a problem once we go on prod with v5 as all submissions will be made from V5. So there will not be a need for real time sync from v4 to v5. |
James is testing fix now in dev. |
Notice that:
These issues will be tracked separately. Closing this issues since Submissions are being synced. |
The text was updated successfully, but these errors were encountered: