Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Email notification with outdated content / setting a delay possible? #23682

Closed
fideliopark opened this issue Jan 24, 2023 · 1 comment
Closed
Labels
Bug This is a bug (something does not work as expected) Issue Stale (automatic label) This issue is stale because it has been open 1 year with no activity. Remove this label to keep open

Comments

@fideliopark
Copy link

fideliopark commented Jan 24, 2023

Bug

I have created an automatic email notification with the trigger "Invoice released".

Unfortunately, the mail always contains outdated content, both in the variables and in the PDF attachment.

Example:
Newly created invoice is released for the first time.
The mail still contains the draft designation "(PROV4)" in the text (for the variable "REF") instead of the correct invoice number.
Also the PDF still has the name "(PROV4)" and the content is still the draft (no invoice number, watermark, etc.).

My guess is that the creation of the mail happens faster than the creation of the document and the associated values and therefore the old status still ends up in the mail.

Is there a solution for this?
Is there perhaps a possibility to set a delay of a few seconds for the creation of the mail, so that all the data is available for sure?

Environment Version

16.0.3

Environment OS

Debian 11 - Linux dolitest 5.15.83-1-pve #1 SMP PVE 5.15.83-1 (2022-12-15T00:00Z) x86_64

Environment Web server

Apache/2.4.54 (Debian)

Environment PHP

7.4.33

Environment Database

MariaDB 5.5.5-10.5.18-MariaDB-0+deb11u1

Environment URL(s)

No response

Expected and actual behavior

No response

Steps to reproduce the behavior

No response

Attached files

No response

Copy link

This issue is stale because it has been open 1 year with no activity. If this is a bug, please comment to confirm it is still present on latest stable version. if this is a feature request, please comment to notify the request is still relevant and not yet covered by latest stable version. This issue may be closed automatically by stale bot in 10 days (you should still be able to re-open it if required).

@github-actions github-actions bot added the Issue Stale (automatic label) This issue is stale because it has been open 1 year with no activity. Remove this label to keep open label Jan 29, 2024
@github-actions github-actions bot closed this as completed Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug This is a bug (something does not work as expected) Issue Stale (automatic label) This issue is stale because it has been open 1 year with no activity. Remove this label to keep open
Projects
None yet
Development

No branches or pull requests

1 participant