SJ77

This bulletin is for versions older than 4.7.0, it should self-dismiss soon since you've recently upgraded.

Yes, there is and it is in your logs. You have a EX0 error there.

Nothing, looks like there is a bug with the current beta - I have a fix pending review.

It is. 8.2 isn’t.

@SJ77 if you still need private help, @teraßyte and I offered to help. Send me or him a PM, and whoever you pick will help you fixing this issue.

It's good advice. Unfortunately have extremely important data, lot's of it.

Then you don't have this app linked to the Marketplace. If you don't have any important data with this app, and you can reconfigure it again, remove it and reinstall it again. 
If you have important data with this app and you cannot remove it, send a PM and I will help you link it to the Marketplace.

@SJ77 While not recommended, there's a way to do it by editing directly the database. I've done it a few times for...reasons.
Send me the info on what you need changed and I can take a look at it while I work on your other tasks. 😉

Once you press on that "Update Available" it will take you the Marketplace in your ACP. Make sure you are logged in from top right side. 

 
Then press on the update button.

When you upgrade from a version older than 4.5, you'll get prompted to complete a Marketplace set up process.
You should see an AdminCP notification for that, follow the instructions to match up your existing third party resources.

We have assisted you in the account email you submitted.

The forum will continue to work in its current state. You simply lose access to all IPS services, including updates, the IPS spam service, support etc.
I would point out, it would be worth ensuring the customisations are updated, and if needed move to a server that supports PHP 8. By running PHP 7, you are actually running a site that could potentially be compromised, as PHP 7 is no longer supported by PHP themselves for security fixes.

That's an issue with a 3rd party application called forms
 
 

Create your custom file and place it in your community root. Then add following to your constants.php file.
define( 'UPGRADING_PAGE', 'file.html' );  

If the screen is just only displaying white, it means that errors are being suppressed. 

Try adding the following to your htaccess:
php_flag display_errors On You can also look in your server’s Apache error logs for details as well. 

bless you. thank you for this!!
I will do everything I can to make this happen!  I promise I’m trying. I really want to get there
 
Thank you so much!!

SMTP is slow, we see it time and time again.
You could then use the SES app on the Marketplace to send your email via HTTP requests instead, which is much much faster.
You could, at your own risk - create a backup etc... remove the queue items with the following query (you may need to add your table prefix if you use one)
DELETE FROM `core_queue` WHERE `app`='core' AND `key`='Follow'; But please try and get upgraded as soon as you can, we no longer support the version you're using.

Are you hitting your emails per second limit with SES?  If so, you might be able to ask them to increase your limit. 

Hi Mark,
thankfully yes, otherwise my fee to pay for AWS S3 would have skyrocketed.... 😂
I used a drastic measure, clean the background actions thing table from the database. Definitely not the best choice to make, but luckily I had just changed php version to the server and cronjob hadn't started migrating data yet.
It would still be useful to have a button to stop actions with: Pause (useful when you have the server overloaded and one thing is not essential) and an Undo and Restore
 

I would need to look back to an old version to confirm (you should really find some time to upgrade to the latest release!) but I believe the notification task from back then does both emails and inline notifications. 
Using SMTP is naturally going to cause these kinds of tasks to be slow (it's really not a fast protocol). You may be able to temporary switch to PHP processing to let them clear up.

These are site notifications I believe, not emails.

If it was sent via SES, it never went out via Exim.  It would have connected via SMTP to SES to send, which would never trigger Exim.  
By default, unless you enable some sort of logging, there would not be anything available from AWS.  I personally use SNS topics to track delivery of emails.  I pipe them to SESDashboard track success/fail, spam complaints, opens, clicks, etc.  It allows me to do exactly what you're trying to do...  prove what happened.  For example, in this case, I can see not only was the message successfully sent, but it was received by the destination mail server AND that the recipient opened the message...  then actually clicked a link inside of that message.  
Clicking on the event log would show more detailed info about the event itself.  

Unless you’ve setup SNS notifications and something to process them (like SESdashboard.com), there is not logs of delivery, opening, and clicking of emails by default. 

It’s because you are focused on the conferencing tools, which are either not meant for streaming to begin with or only offer streaming for a lot of money. 
Look for streaming solutions. On platforms like YouTube, live streaming with multiple people (and open invites) is a very normal thing and like I said, there are tons of free and commercial solutions available which can feed into platforms like YouTube. Online solutions for this can even push the stream out to all big platforms at once.