Is there a limit to quantity of post functions on an event-based action JMWE
Asked by Jennifer Marple:

On a JMWE event-based action (or other types) - is there a recommended or firm limit to how many post -functions can be setup?

We are experiencing performance issues that I believe are possibly related to a very complex action with many post-functions that I setup yesterday and modified this morning. My post functions are conditional to certain string matches using a nunjucks statement.

I can't even get JMWE to load right now, and existing actions appear to not be running. I do have a ticket in to Atlassian as well to work through that.

Cloud-based JSM.


Answers:
author: Pablo Vergara (Appfire)
body: Hi [@Jennifer Marple](/t5/user/viewprofilepage/user-id/5423895) / [@Stephen Dyball](/t5/user/viewprofilepage/user-id/5350356)

Just to confirm, we are aware of the issue affecting our JMWE users.

**Our engineers are actively working with the development team and Atlassian to resolve this issue as quickly as possible.** We understand how frustrating this can be and sincerely apologize for any inconvenience this may have caused.

Please rest assured that we are doing everything we can to fix the problem and will provide you with updates as soon as more information is available. We appreciate your patience and understanding during this time.

Thanks,

Pablo Vergara,  
*Senior Support Engineer - Appfire*


author: Jennifer Marple
body: For those following along - I received [an update that service is restored](http://status.innovalog.com/incidents/nkftzz771jkk) now.   

So - I'll flag this as answered - but - if anyone knows if there IS a limit (recommended or firm) on post-functions, let me know!  

<br />

comments: author: Amelie Winkler _Appfire_
body: Hi [@Jennifer Marple](/t5/user/viewprofilepage/user-id/5423895) -- I'm part of the Appfire team, and I can confirm that there's **no limit on the number of** **automations** you can set up with JMWE!

While we generally recommend streamlining automations to keep your workflows efficient, you can technically run unlimited automations (whether that's workflow-based automations or event-based/scheduled actions).

The slow loading issue you experienced was unrelated and has been fixed by our development team. If you still have issues, please check the "Apps" section to ensure you have the latest version installed.

As my colleague [@Pablo Vergara (Appfire)](/t5/user/viewprofilepage/user-id/5180606)mentioned, we're sorry about the disruptions this may have caused you!


author: Matt Boyd
body: We are also experiencing issues where JMWE products are not working as expected. If you check your audit logs within the App management page you you might see a failure within an update that was pushed this morning. We are currently experiencing issues across 4 environments relating to JMWE products.   

Attempting a work around to separate a sequence of post functions worked briefly but since 1:50pm BST we have been experiencing major JMWE related issues.   

A support ticket has been raised with AppFire for investigation however they are not moving quickly on investigating the issue

comments: author: Jennifer Marple
body: Glad to know I'm not alone and that it might "just" be a platform issue vs something I broke. Hopefully it's fixed soon! I've logged my own Appfire ticket as well.


author: Matt Boyd
body: [@Jennifer Marple](/t5/user/viewprofilepage/user-id/5423895) if you are able to load JMWE logs (that might be your first trouble) you can change the filter to show errors.   

We are seeing issues with "internal-Error" and "Error while fetching JMWE migration problems" message types. with the message referencing "Request took too long. Cancelling" which looks like the tool is failing to connect to a service somewhere.   

Having seen these issue before it looks to be a platform issue and not an issue that you've caused.   


author: Stephen Dyball
body: Hi [@Jennifer Marple](/t5/user/viewprofilepage/user-id/5423895) - we're experiencing issues with JMWE at the moment, so I don't think it's anything you have done.

We've raised a support request to Appfire to look at the issue, it might be worth you doing the same :)

Link to the support portal is here: <https://appfire.atlassian.net/servicedesk/customer/portal/11>

comments: author: Jennifer Marple
body: Thank you! Glad to know it might not be a me problem :D   

I will log a ticket as well.


author: Avinash Bhagawati _Appfire_
body: Hi [@Jennifer Marple](/t5/user/viewprofilepage/user-id/5423895) ,

Good day!

Please accept our apologies for what you have experienced.

We identified that there was a JMWE outage that occurred on June 5, 2024, due to an issue with the JMWE API token. After our investigation with Atlassian, we have rolled the app back to its previous version to restore access. It is operational now.

If you have any questions meanwhile, please open a support ticket on our portal at <https://appf.re/support>

Thanks,  
Avinash


Tags: addon-com.innovalog.jmwe.jira-misc-workflow-extensions

cloud

jira-service-management

jira-service-management-cloud

jmwe