Intermittent Failure to Open Loading Modal – trigger_id Expired

[kranti-rh]

I'm experiencing intermittent failures when attempting to open a loading modal due to an expired trigger_id.

My implementation ensures that the modal is triggered immediately upon receiving the trigger_id, well within the 3-second validity period.
Despite this, the request to open the loading modal occasionally fails, indicating that the trigger_id has expired.

Questions:

1. Has this issue been reported previously? Are there any known factors that might cause the trigger_id to expire prematurely?
2. Could this be due to network latency or other Slack-side processing delays?
3. Are there any recommended best practices or alternative approaches to ensure reliable modal opening?
4. Looking forward to insights or guidance on resolving this issue.

Thanks!

Reproducible in:

[INFO] +- com.slack.api:bolt:jar:1.38.3:compile
[INFO] |  +- com.slack.api:slack-api-model:jar:1.38.3:compile
[INFO] |  +- com.slack.api:slack-app-backend:jar:1.38.3:compile
[INFO] +- com.slack.api:bolt-socket-mode:jar:1.38.3:compile
[INFO] +- com.slack.api:bolt-jakarta-servlet:jar:1.36.0:compile
[INFO] +- com.slack.api:slack-api-client:jar:1.36.0:compile

[zimeg]

Hey @kranti-rh 👋

This might be related to networking issues in #1438, but I'm interested in learning more about these failed requests too!

My implementation ensures that the modal is triggered immediately upon receiving the trigger_id, well within the 3-second validity period.

Is there a chance you can share debug logs of a failed request? I'm especially interested in knowing how often this does fail and how long successfully requests take to complete.

Any more info is also helpful, but do let me know of possible networking issues that could be getting in the way as well 👾