We have a simple automation that checks an S3 bucket every 30 seconds and triggers a workbench when a file is added to the bucket. It all seems to work fine, except I noticed today that although the automation was still running it was not triggering the workbench when new files were added to the bucket. Looking at the automation log I see...
Service Unavailable (Service: Amazon S3; Status Code: 503; Error Code: 503 Service Unavailable; Request ID: 4F1445BF8D4DF69F; S3 Extended Request ID: bNSlvkHBzAjPZYX7hSRdG86fwpdaYqp2WrrGNa0IpPm4Qk4XeLb9qRXDdUk5EkWY/NdK1PcNYahUZduRItZf4t9NeiHv1+A8juV+dCYgLfc=)
It appears that there was an intermittent issue that caused the 503 error. When this happened the automation continued to run, but no longer worked correctly (new files were added to the S3 bucket, but the automation did not trigger the workbench).
I added a notifier to the S3 Trigger in the automation so I can be notified of future failures, but wondering if there is another solution to resolving the issue so the automation will continue to work correctly even if it gets an occasional 503 error. I see that you can configure automated retries (https://community.safe.com/s/article/Configuring-Guaranteed-Delivery-in-FME-Server-Automations-with-Automated-Retries), but I presume this is only for when the workbench fails and not the automation trigger. Thanks! - Jorma