Thanks. I remove the return and tried to run the sync job but I still can’t see the old events.
Should I restart the server? Create a new sync event?
You can try to restart the server
I restarted and tried to sync again but no luck. I will try setting up new event sync with a new class
Once I create a new event sync it pulled all historical data and also was able to pull the first new mint very quickly. However the second time it didn’t work and it’s stuck again.
Is it possible the problem is related to the fact that I’m modifying the schema (adding extra fields) to the Class used for the sync event in the aftersave cloud function? Maybe I’m not supposed to do that
I still see things like {"_objCount":1642,"className":"Created","id":"wn3vwyRGuWUXkypGB6pRlmu9"}
It looks like you still have an infinite loop
same thing now with {"_objCount":10929,"className":"Created","id":"XBp1yO5iepGMTIcTyK0sGlkA"}
I removed all “await” from the afterSave function and it seems to be syncing now
Can you please let me know if you still see infinite loops going on? That will be obviously a concern in terms of performances
I still see them now:
{"_objCount":95093,"className":"Created","id":"QlxQItxuCpnrE8aIYpWRVSZ7"}
{"_objCount":95095,"className":"Created","id":"kp6B3RZ3grGsjsfbOaRYZL3l"}
{"_objCount":95096,"className":"Created","id":"XBp1yO5iepGMTIcTyK0sGlkA"}
What is _objCount? I can see those objects in the created Class but not sure what objCount means
it looks to be how many times that loop iterated, now it is {"_objCount":300728,"className":"Created","id":"QlxQItxuCpnrE8aIYpWRVSZ7"}
Can you see anything in your logs in dashboard or you have a blank white page?
instead of logger.info(uid);
you should use logger.info(JSON.stringify(uid));
that would be for every logger.info that you use, you may see the logs after that and after you reset the server again
Where can I log the _objCount? So I can debug from my side
Thanks, I got rid of the logger all together and CPU is back to normal (20%) which is a step forward.
Still I can’t see the logs though
maybe you don’t have anything in logs yet if you removed all logger.info
can you add back your logger.info and this time using JSON.stringify?
what you get now as error should be fixed with a server restart