• Resolved markussss

    (@markussss)


    I am not sure if this is only happening to a single site or all as it’s unusual to see “failed” emails in the log. However, I have a site that shows failed emails. When I switch from Email Logs “All Statuses” to “Failed” it does not show a single email.

    I know at least from the past (and other sites) that this used to work as it should

    Could this be a new bug? Or maybe really site related?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Ibrahim Sharif

    (@ibrahimsharif)

    Hello @markussss,

    We haven’t observed this issue on our end, so it’s likely something specific to your site’s environment is causing the problem. Based on your description, and considering that the filter used to work correctly, it’s possible a conflict is interfering with FluentSMTP’s ability to accurately identify and display failed emails.

    To help us pinpoint the cause, could you please check your browser console for any errors while viewing the Email Logs page and specifically when switching to the “Failed” filter? These errors can give us valuable clues about what might be going wrong.

    Here’s how to access the browser console:

    1. Launch your browser (e.g., Google Chrome, Firefox, Safari, etc.).
    2. Right-click on the webpage and choose “Inspect”, or use the shortcut “Ctrl + Shift + I” (Windows) or “Cmd + Option + J” (Mac).
    3. This will open the Developer Tools window either at the bottom or the side of your screen.
    4. Navigate to the “Console” tab within the Developer Tools window.

    The console will display error messages, logs, and other pertinent information related to the webpage.

    The issue you’re experiencing could stem from various factors, including your server configuration, hosting environment, the presence of a security plugin, or even firewall settings that might be interfering with FluentSMTP. The browser console output can help us narrow down these possibilities.

    Please share the console output with us, and we’ll be happy to investigate further and offer specific recommendations. We’ll work with you to get this resolved!

    Thread Starter markussss

    (@markussss)

    Hello,

    I could not reproduce it myself now. So that means it was not even site related some somewhat session or browser related. Sorry, false alarm.

    best regards
    Markus

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.