Bug on report - sending SMS

AppSheet AppSheet Q&A
,
1

Hi all,

I’ve been meeting an issue for a few days now, cannot find where that comes from.

My report does not work anymore on the schedule way, but I have to run it manually.
Here are the settings :

2X_c_ca6ca8485e902d856f5e73d37c07287e2e24b131.png
2X_c_ca6ca8485e902d856f5e73d37c07287e2e24b131.png2122×1084 82.6 KB

Once again, nothing goes at 12:20AM, but if I click on “Run” button, the recipients receive their SMS.

I was suspecting any trouble on the “If this is true” section, but that does not make sense to have trouble here and beging able to send successfully messages through the “Run” button.

Do you have any clue about this issue ?

Many thanks

Aurelien

2

What is the If this is true expression?

3

AND(

IN([Barcode Employe],ListingMvtsJour[UtilisateurResponsableActuel]),

[Barcode Employe]<>“169”,
[Barcode Employe]<>“100”
)

ListingMvtsJour is a slice from a Table “Outillages”, based on [Date chgt Statut] column which is a timeStamp column

4

Running the workflow manually from the app editor bypasses the If this is true condition, so we can reasonably conclude the problem is with the condition. Have you tested the condition in Expression Assistant?

5

Yes, it seems OK ?

2X_c_c253f10ba986f543bbea032fd69876695a30d704.png
2X_c_c253f10ba986f543bbea032fd69876695a30d704.png1280×509 30.3 KB

Here is what I have in the slice data:

2X_b_ba9014062c4f07dbcb6b79949eba11b3f0b3425b.png
2X_b_ba9014062c4f07dbcb6b79949eba11b3f0b3425b.png1568×265 28.3 KB

The OK relates to the one expected but not received;the 169 is OK not to receive it

6

Use the Test button in Expression Assistant to test.

7

Sorry for misunderstanding your resquest

Here is the result : seems to meet what I expected (I had a look on the whole result, only two gave a “Yes”, this is an extract):

2X_d_dfdfc3f5a9c6a844e0d77396ce1034b19ce318bd.png
2X_d_dfdfc3f5a9c6a844e0d77396ce1034b19ce318bd.png2438×696 31.9 KB

1 Like
8

The next step is to try this:

9

Hi @Steve,

Thanks. The report is supposed to be fired at 12:20AM, so I will keep you informed of the log content when I’ll have it. Here it’s currently 7:36AM, so it will be a little later.

1 Like
10

Hi @Steve

I eventually got it : I probably made a mistake on scheduled time : I use to work with a 24h-based time, so I think I wrote a mistake.
I got new informations : all SMS were pushed, but at 00:20am (middle of the night for France)

Here is what I got, and log in the Twilio system:

2X_5_5b1e1776081d0cd5f4d3514103d4f357c53e542d.png
2X_5_5b1e1776081d0cd5f4d3514103d4f357c53e542d.png2250×1113 95.3 KB

I changed it for:

2X_1_1286ea74a0564333b4201832821315251db9c7a6.png
2X_1_1286ea74a0564333b4201832821315251db9c7a6.png2053×375 17.2 KB

I will see today if this new setting matches what I expect.
I’ll let you know !

1 Like
11

So,

with the new setting, nothing has been pushed at expected time : 12:20am (which is, for me, twenty past twelve, in the middle of the day).
That will be probably pushed around midnight, like yesterday.

Do you have any idea of what I should write for having it ?

12

Hmm… 12:20am is 20 minutes after midnight. If AM or PM occur in a time, the time is in 12-hour format, not 24-hour format.

Unfortunately, I’m just not familiar enough with SMS notifications and Twilio integration to help you further. I recommend you engage support@appsheet.com for more help.

13

dev:

with the new setting, nothing has been pushed at expected time : 12:20am (which is, for me, twenty past twelve, in the middle of the day).

@dev
“…twenty past twelve, in the middle of the day…” is actually 12:20pm, not 12:20am…12:20 am is pure midnight as per 12h time.

1 Like
14

ok.
I will try this one then !
Thank you for your help

I’ll let you know, @Steve and @LeventK !

1 Like