Skip to main content
Question

"Deadline Exceeded Error code 6 " while running the compound action

  • January 27, 2026
  • 1 reply
  • 12 views
M
Forum|alt.badge.img

We are working on a use case , where we get invoices from databricks , with requesters username, associated with that . what our current flow does is that , it fetches username for each invoice gets its email and fetches the profile of the user to get the email and region of the user and also to fetch the manager information to send the invoice escalation notification if an invoice hits deadline on that particular day. So the logic works in a way that it runs daily , and groups invoices based on their ages and as per the requester and managers and sends those to the respective people. This is flow is working successfully . But theres is a catch . On Biweekly Wednesdays we have the logic to pull all invoices above a certain number of days. So it fetches thousands of invoices on Biweekly wednesdays and then tries to process them. But while processing the script gives an error saying “ Deadline Exceeded” with the error code 6. As we are not calling any external API why is the code failing . Is there a platform specific limit for Moveworks compound action that stops the flow from running after running for a certain amount of time . If that's the case how could one handle this ?

On normal days - API fetches 400 max invoices - All users gets notification
On biweekly Wednesdays - API fetches 4000 invoices - The flow fails giving the Deadline Exceeded error. 

I am open to suggestions on this. Would love the help.

Thanks

1 reply

rgeroulo
Forum|alt.badge.img
  • rgeroulo
  • Employee
  • January 27, 2026

Hi ​@mandarmarkandeya!

Is the error being thrown by an Script Action? Per this verbiage “But while processing the script gives an error”.

Regardless, fetching 4000 objects and processing them in a flow could definitely lead to a timeout due to the Size Limits. For Script Actions, the size limits are the following for example:

  • Your code can't be too long (4096 bytes)
  • Your lists can't have too many things in them (2096 bytes)
  • Your numbers can't be too big or too small (4294967296)
  • Your words (strings) can't be too long (4096 bytes/characters)

To work around any size limits, I would recommend paginating the response that needs to be processed. This logic would be the following:

  1. Retrieve first 0-200 invoices
  2. Run logic and send notifications
  3. Retrieve invoices 200-400 using API parameter like offset=200
  4. Run logic and send notifications
  5. Retrieve invoices 400-600 using API parameter like offset=400
  6. Run logic and send notifications
  7. Retrieve invoices 600-800 using API parameter like offset=600
  8. etc….

This loop would end when your API response is empty.

Let me know if you have any questions as this should help workaround any timeouts you are seeing.

Best,

Ryan

    Terms & ConditionsCookie settingsAccessibility statement