Hi team,
I need some help with the custom app. Our app performs a bulk action, but it occasionally times out (after 20 seconds). The framework now supports jobs that can run for up to 2 minutes. However, when I check the job documentation, I see that job creation is only being handled on the client side, not the server side. How can I initiate and manage jobs from server.js?
Thanks
I want to trigger the job creation in server.js, not on the client side.
The job feature is restricted on the serverless side. It can only be triggered from the client side.
If you could share your use case in detail and why you want to trigger the job from the serverless, I can share this feedback with the team to consider this ability.
I can also suggest any alternative for now, if available.
Hi @Raviraj ,
In our app, provisioning and de-provisioning to the IAM applications, it involves multiple API calls [ fs api(requester email, service request details, JC api(Add/remove to group, get user id, get group id) ], which sometimes cause timeouts. Our app is fully dependent on the ticket update event, with no UI or client interaction in the process only server.js is used.
To address the timeout issue, we plan to enhance the app by using the job method. This will help manage longer processing times and prevent timeouts.
In addition to that, I have added a timer to each API call to track which API takes the most time. I noticed that on the timeout tickets, the FS API takes half of the total processing time.
@Dhananjezhian_Janart Thanks for sharing the use case.
Your use case sounds valid for the job use. But, the Job feature also comes with concurrency limits, which would limit its use for a huge volume of tickets.
So, let me share your use case with our team to consider the availability of the job trigger function from serverless. But, we cannot commit any time for it.
Thanks! @Raviraj, I’m really looking forward to your input; it’ll be super helpful for us as we move forward with development.