Same problem here with FMS14.0.4 on Windows2012 server, see No Scripts are available for the specified account.
You must indeed keep pushing the next button ten or twenty times until the dialog continues.
However: then the following problem in script scheduling reveales itself.
It is impossible to create a schedule which runs every 15 minutes or so.
And the schedule dates seem to be shifted to one day ahead.
See the picture: this schedule is clearly set to run every 20 minutes: it simply won't do that.
Bugs like these cost us, developers, so much time and effort to find solutions or create workarounds.
Am I the only one with this problem or did other developers notice this as well?
If so, did you find a solution?
Second problem with respect to scheduling is solved.
If you start a new schedule at - for instance - 22.30 and want it to run every 15 minutes during the day, then don't set starting time at 22.30 and end time at 22.15 (next day).
Set Starting time - for instance at 00:05 on the starting dat and end time at 23:50.
I never ran into the second issue. I have a script that has run every 3 minutes, reliably for more than 5 years. I think the only thing that would cause an issue with a short interval between script runs would be if the script did not finish in time for its next run to begin.
However, the main issue is still the fact that "No scripts are available for the specified account." persists as a nuisance. I have pressed next a half dozen times, but I don't have the patience to go as far as 20 times.
Can you please try to press next until the dialog continues?
If this works with you as well, then we know that this is a temporary solution until Filemaker comes with a fix.
You mean you want to to press the NEXT button indefinitely or count the number of times it takes to dismiss the "no scripts available" message? I can tell you that it sometimes takes 1 click, but if 2 clicks don't do it I have no interest in being a guineau pig for this. It's enough, in my opinion, to report it to FileMaker and let them know about it. I don't know enough about HTML-5 to understand what makes it happen.