8 Replies Latest reply on Sep 3, 2015 12:31 PM by electon

    FM GO script took three hours to complete.  What might cause that?

    TomEdge

      Screenshot 2015-09-03 15.43.44.jpg

      This script began execution at 11:13:47 AM when a variable was set for the start time and finished at 2:14 PM when the record was added to this table.  This is the first time I've seen this happen in over 11,000 transactions.  Does anyone one know what would cause a script to take 3 hours to execute or hang for that long on an ipad?  If FileMaker Server reached its connection limit could it cause this?

        • 1. Re: FM GO script took three hours to complete.  What might cause that?
          TSGal

          TomEdge:

           

          Thank you for your post.

           

          Your description doesn't provide enough information.  For instance, what does the script do?  Are there a lot of script steps?  If another client has a record locked, is it possible the script is waiting for that record to become unlocked?

           

          Any other information you can provide may be helpful in narrowing down the possible cause(s).

           

          TSGal

          FileMaker, Inc.

          • 2. Re: FM GO script took three hours to complete.  What might cause that?
            TomEdge

            It's a fairly complex script  used to start time tracking of specific activities.  One of the first things the script does is check to see if that person is already clocked into an activity; if they are the script exits so no user is punched into the same activity twice.  In this case, the user noticed saw on the main screen that they were not punched into the activity so they clocked into it again at 11:23 AM.   (They couldn't confirm which iPad they used...)

             

            So while the first transaction was hung up, the script executed the identical second transaction with no problem and punched them in to that activity.  Since the first attempt hadn't yet been written to the table it didn't stop the second transaction.  Later, when they told me that they were punched into the same activity twice, I told them that was impossible.  Than I discovered the record above...

            • 3. Re: FM GO script took three hours to complete.  What might cause that?
              TSGal

              Tom Edge:

               

              Thank you for the information.

               

              Is it possible the client switched to another application while the script was running?  The script would have paused until the client switches back to FileMaker Go.

               

              In the privilege set for that client, what value do you have for fmreauthenticate extended privilege?  This will let me know whether the script can continue if it is paused.

               

              TSGal

              FileMaker, Inc.

              • 4. Re: FM GO script took three hours to complete.  What might cause that?
                TomEdge

                It is checked.  Everyone logs into the app as Guest with no password and data entry only access.  I suppose it is possible that they bumped the home button.  In the event that happened I wouldn't want the script to pause.  Is there a way to control FM behavior in the case of an app switch?

                Thanks, Tom

                       From: TSGal <noreply@filemaker.com>

                To: Tom Edge <tomedge@yahoo.com>

                Sent: Thursday, September 3, 2015 11:22 AM

                Subject: Re:  - FM GO script took three hours to complete.  What might cause that?

                    

                #yiv8809864698 * #yiv8809864698 a #yiv8809864698 body {font-family:Helvetica, Arial, sans-serif;}#yiv8809864698 #yiv8809864698 h1, #yiv8809864698 h2, #yiv8809864698 h3, #yiv8809864698 h4, #yiv8809864698 h5, #yiv8809864698 h6, #yiv8809864698 p, #yiv8809864698 hr {}#yiv8809864698 .yiv8809864698content p #yiv8809864698 .yiv8809864698content li #yiv8809864698 .yiv8809864698button td {}#yiv8809864698 .yiv8809864698footer #yiv8809864698 .yiv8809864698footer a

                |

                 

                 

                |

                FM GO script took three hours to complete.  What might cause that?

                reply from TSGal in Discussions - View the full discussionTom Edge: Thank you for the information. Is it possible the client switched to another application while the script was running?  The script would have paused until the client switches back to FileMaker Go. In the privilege set for that client, what value do you have for fmreauthenticate extended privilege?  This will let me know whether the script can continue if it is paused.

                 

                 TSGalFileMaker, Inc.

                Reply to this message by replying to this email, or go to the message on FileMaker Community

                Start a new discussion in Discussions by email or at FileMaker Community

                Following FM GO script took three hours to complete.  What might cause that? in these streams: Inbox

                 

                |

                 

                 

                Manage your email preferences

                 

                FileMaker Developer Conference 2016 • Las Vegas, Nevada • July 18-21 • www.filemaker.com/devcon

                 

                  |

                • 5. Re: FM GO script took three hours to complete.  What might cause that?
                  DavidJondreau

                  You're saying the dtStart is the time the script starts and dtEnd is when the script ends? You've got a bunch of other start and ends in that list that are 2+ hours long. Why is this one different?

                  • 6. Re: FM GO script took three hours to complete.  What might cause that?
                    Markus Schneider

                    I have a small CF that can be called everywhere in a script. It writes a timestamp, a comment and the delta-time into a global variable. This $$var can tell You where a script took how much time. It won't tell You if a user switched to another app..

                    • 7. Re: FM GO script took three hours to complete.  What might cause that?
                      DavidJondreau

                      You probably should change this around so that a record is created at the start of the script. Two people could open the same task if they try at close to the same time (between the script checking and creating the record).

                       

                      In fact, could that have already happened in the course of 11K transactions, but there were no repercussions so you don't know?

                      • 8. Re: FM GO script took three hours to complete.  What might cause that?
                        electon

                        From the FmGO documentation:

                         

                        When you switch to another app, FileMaker Go enters a suspended state unless there is an audio or video file playing.

                        When you return to FileMaker Go, the app and scripts resume from where they left off.

                        For hosted files, if any of the records in the data set that a script is acting on were modified while FileMaker Go was suspended, the script aborts. If none of the records were modified, the script continues.


                        1 If you switch away from FileMaker Go for an extended period, and iOS forces the app to quit, FileMaker Go attempts to generate a hibernation file. When you restart FileMaker Go, it uses the hibernation file to reopen files.

                        A hibernation file is not generated when a script with Allow User Abort set to Off was running when you switched away from FileMaker Go.

                         

                        Maybe there's a hint there.