FM BetterForms
BF Editorfmbetterforms.com
1.0 dont use
1.0 dont use
  • Introduction
  • Features Summary
  • Getting Started
    • System Overview
    • Integration
      • 1. Configure FileMaker Server
      • 2. Add your Server to BetterForms
      • 3. Introduction to Hooks
      • 4. Create your first Site
      • 5. Create your first Page
      • 6. Configure your FileMaker File(s)
      • 7. Run your first Hook
      • Next Steps
    • Common Customizations
      • Introduction to Actions
      • Introduction to Buttons
      • Page Navigation
      • Displaying Data in a Table
    • Support
      • Hacking a Webpage
      • Learning JSON
  • Reference
    • Site Settings
      • Navigation
      • Slots / Code Injection
      • App Model
      • Site-wide Named Actions
    • Page Settings
      • Data Model
      • Card / Window Modals
      • Validation
        • Custom Validators
      • Misc Page Settings
    • Page Elements
      • Common
        • Button
        • Data Table
        • HTML
      • Grouping Elements
        • Tabs
        • panel
        • accordion
        • listrows
      • Uploading Files
        • dropzone
        • dropzone to S3
        • uploadCare
      • Misc Elements
        • Plain Text / Code Editor
        • signature
        • fullCalendar
        • rangeSlider
      • Payment Gateways
        • Authorize.net
        • PayPal
        • Stripe
      • Adding Custom Page Elements
    • Actions Processor
      • Named Actions
      • Actions
        • runUtilityHook
        • path
        • debounce
        • throttle
        • showAlert
        • showModal / hideModal
        • function
        • clipboard
        • cookie
        • setFocus
        • wait
        • emit
        • validate
        • channelJoinAnon
        • channelLeaveAnon
        • messageSend
        • messageSendAnonChannel
      • Authentication Actions
    • Script Hooks
      • Globals Variables
        • $$BF_Model
        • $$BF_App
        • $$BF_State
      • Keeping Keys Private
      • Reducing Payload Size
      • API Callback Endpoint
      • Common Hooks
      • Scoped Hooks
    • Users & Authentication
      • Managing User Accounts
      • Custom Login Pages
    • Advanced Configuration
      • Custom Domains
    • BF Utility Functions
    • BF Error Codes
    • Messaging
      • Adding users to channels
      • Removing users from channels
      • Sending messages
      • Get connected users
      • Get active channels
  • Usage Tips
    • Troubleshooting
      • Debugging
      • Frozen Actions Queue
    • JavaScript Tips
      • Calling Named Actions from HTML Vue Events
      • Calculations
    • System Overview
    • Forms Processor
      • Form Types
      • HTML & VueJS
      • Styling and Design
      • JS Caclulations and Functions
    • Customizing and Styling
      • Custom Components
      • Custom CSS
      • Custom Components
      • Page Pre-loaders
      • Favicon
    • Design Patterns and Best Practices
      • Working with environments
      • Handling Data
      • Saving Data
      • Optimization
      • Business Logic
      • UI / UX
  • Security
    • Authentication
    • Security White Paper
    • Firewalls
    • Technology Stack
  • Compatibility
Powered by GitBook
On this page
  • How to check the Actions Queue
  • How to find the broken action
  • Common reasons for broken actions

Was this helpful?

  1. Usage Tips
  2. Troubleshooting

Frozen Actions Queue

If your page seems unresponsive, one thing to check is if the actions queue has frozen. The actions queue is an array that stores upcoming actions waiting to be executed. Most of the time, it should be empty because most actions execute very quickly. However, if an action is hanging, the queue will not continue to execute and each new click of a button with actions will simply add to the queue but not seem to do anything.

The easiest recognized symptom of a frozen actions queue is when you click a button and that button doesn't work, but after refreshing the page, the button does work as expected. This is because refreshing the page clears the actions queue.

How to check the Actions Queue

To inspect the current state of the actions queue, go to the console in your browser and type the following command:

window.vueapp.$store.state.actions.actions

This will return the actions queue array. If the array is empty, all the actions in your queue have executed. If it's not empty, there is an action still executing and the actions listed here are waiting to execute.

How to find the broken action

For this, you need to do a bit of detective work and retrace your steps. If your actions queue is frozen, the action that is currently being executed will not be shown to you. However, since you know that the first action in the actions queue array comes immediately after the broken action, this should help you locate exactly which action is not completing its execution.

Common reasons for broken actions

  • A path action is missing the path or url option

PreviousDebuggingNextJavaScript Tips

Last updated 3 years ago

Was this helpful?