Troubleshooting

Use this page when an automation, notification, or outbound email scenario is not behaving as expected.

License Missing, Invalid, Or Expired

Checks:

  • Open Operations Automation License and review License Status and License Expiry.
  • Confirm the "Allow HttpClient Requests" is enabled on Operations Automation Extension Settings
    • Open Extension Management
    • Click Operations Automation to Open Settings
  • Confirm the notification email and contact details are populated.
  • Run Refresh License.

Typical outcomes:

  • The app may report that the license is not registered.
  • The app may report that the current license is invalid or expired.
  • Feature-specific jobs may remain unavailable until license information is valid.

If the error continues after these checks, contact Lonicera Support.

No Email Account Registered

Checks:

  • Confirm at least one Business Central email account is registered.
  • Reopen the relevant Operations Automation page to see whether the app still warns that no email account is registered.

Typical cause:

  • Notifications and outbound emails cannot send until a Business Central email account exists.

Email Scenario Not Assigned

Checks:

  • Open Email Scenario setup in Business Central.
  • Confirm the Operations Automation scenario is assigned to an email account.
  • If outbound jobs use generic email sending behavior, also confirm the Default scenario is assigned where required.
  • Re-run a controlled notification test and review the entry logs.

Typical causes:

  • An email account exists, but the Operations Automation email scenario has not been assigned.
  • The sending flow falls back to behavior that depends on the Default email scenario and that scenario is also unassigned.

Notification Not Sent For A Status

Checks:

  1. Open Operations Automation Status and confirm Send Email Notification is enabled for the finished status.
  2. Open the specific Operations Automation Setup and confirm the same status is enabled there.
  3. Confirm recipient addresses or Send To Job Entry Owner are configured.
  4. Review the entry logs for a warning stating that sending email is disabled for the status.

Important rule:

  • A status must be enabled both in Status Setup and in the individual setup before the app sends notification emails.

Entry Stuck In Waiting

Checks:

  • Confirm the setup is not blocked.
  • Confirm the related setup queue and job queue records exist.
  • Confirm the job queue can run the configured object.
  • Confirm filters are not excluding all expected source records or preventing downstream work.

Typical causes:

  • Blocked setup
  • Missing or paused job queue execution
  • Incorrect object or filter configuration

Entry Stuck In Process

Checks:

  • Review the last log entries for the entry.
  • Confirm the owning job queue entry is still running or has completed.
  • Check whether an exception interrupted processing before the final status update.

Typical causes:

  • A failed object execution
  • A downstream email or report generation issue
  • Job queue contention or incomplete cleanup of ownership fields

Reprocess Unavailable Or Failing

Checks:

  • Confirm the entry is in a status that supports reprocessing.
  • Review whether a reprocess reason is required by the setup.
  • Confirm the original source context still exists.

Typical causes:

  • Unsupported status for reprocess
  • Missing reprocess reason
  • Source record or setup no longer valid

Customer Statement Automation Not Triggering

Checks:

  • Confirm the customer statement feature is enabled.
  • Confirm an Operations Automation Setup exists for the customer statement queue or email process.
  • Confirm customer selection filters include the intended customers.
  • Confirm report selections for customer statements are configured.
  • Confirm customer email addresses are available.

Typical causes:

  • Feature not enabled
  • No eligible setup found
  • Filters excluding customers
  • Missing report configuration

Posted Sales Invoice Automation Not Triggering

Checks:

  • Confirm Email Invoice Job is enabled.
  • Confirm an Operations Automation Setup exists for the invoice email codeunit.
  • Confirm setup filters include the intended bill-to customers.
  • Confirm posted sales invoice report selections and layouts are configured.
  • Confirm customer email addresses are available.

Typical causes:

  • Feature disabled
  • No eligible setup found
  • Filter mismatch
  • Missing customer email
  • Missing report selection or layout

Vendor Remittance Advice Automation Not Triggering

Checks:

  • Confirm the vendor remittance feature is enabled for your environment.
  • Confirm an Operations Automation Setup exists for the vendor remittance email codeunit.
  • Confirm setup filters include the intended vendors.
  • Confirm vendor remittance report selections and layouts are configured.
  • Confirm vendor email addresses are available.

Typical causes:

  • Feature disabled or unavailable
  • No eligible setup found
  • Filter mismatch
  • Missing vendor email
  • Missing report selection or layout

Attachment Export Unavailable

Checks:

  • Confirm the entry or log actually has a source or target attachment.
  • Confirm the setup allows export for the relevant document direction.
  • Review logs for attachment-related warnings.

Typical causes:

  • No attachment stored
  • Export not allowed by setup
  • Export attempted from the wrong entry or log context