Just update the data. You clearly already have a session ID if you can post events, so why not just call the REST API and cut out the middleman?
Create a large field on your event, send a JSON payload through the Platform Event. Deserialize in your Platform Event Trigger, and do whatever post-processing you need to.
As stated in Hosting a Discord.js bot for free using Heroku, if your app is based on Node.js, it looks like you need to put only one line of code there.
worker: node name_of_bot_file.js
If your're using Python, the line is quite similar (more sophisticated answer available at Stack Overflow: How do I host my discord.py bot on heroku?):
Apex batch processing is not a good solution for a one-time operation inserting 6.5 million records from an external source.
You want the Bulk API, which is specifically designed for manipulating data via ETL in very large volumes. There are many Bulk API clients available, including the Salesforce Data Loader, Workbench, Amaxa (which I wrote), and various ...
Heroku connect does not have this kind of configuration anywhere in the dashboard. The reason for that probably is because the number of records to be synced should be driven by the user with whom the Heroku authentication is done.
If you want a specific condition to be fulfilled, I suggest you create an API user which has access to only the records you ...
It depends on whether this is a one-time load, or frequent sync process.
For one-time loads, the standard approach for up to 5 million records is to use the Data Loader. To speed up the processing, load a case with SF to request deferred sharing calculation. Also see if you can disable triggers and workflows.
I faced totally same problem.
In my case, I contacted SendGrid support and asked to activate my SendGrid account.
In two working days, they reactivated my account with their apology.
And now my app successfully send email.
Please try this. Good luck.
Here is SendGrid support:
Your WS path looks good to me it may an issue on the server side.
Here's how I build the WS URL on the client side to run on local and Heroku:
const wsUrl = (window.location.protocol === 'http:' ? 'ws://' : 'wss://') + window.location.host;
i think we need to change the procfile slightly
an i have installed yarn. that could be the case also.
so change the procfile file
web: npm run serve
web: npm start
and add one line in package.json
"serve": "lwc-services serve",
//for above line, when you build the app on heroku it was looking at this script. so i ...