Scheduled trigger module does not work

Forge
1

Hello Atlassian Community,

We are currently developing a Forge app with a Scheduled trigger module as documented here: https://developer.atlassian.com/platform/forge/manifest-reference/modules/scheduled-trigger/.

However, recently the trigger would not fire and no logs are available in the production environment.

manifest.yml

modules:
  webtrigger:
    - key: sync-access-groups-users-jsm-webtrigger
      function: runWebtrigger
  scheduledTrigger:
    - key: sync-access-groups-users-jsm-scheduledtrigger
      function: runScheduledtrigger
      interval: 'hour'
  function:
    - key: runWebtrigger
      handler: index.runWebtrigger
    - key: runScheduledtrigger
      handler: index.runScheduledtrigger
app:
  id: ari:cloud:ecosystem::app/APP-ID
permissions:
  scopes:
    - 'read:jira-user'
    - 'read:jira-work'
    - 'write:jira-work'
    - 'manage:jira-project'
    - 'manage:jira-configuration'
  external:
    fetch:
      backend:
        - 'api.atlassian.com/*'
        - 'https://xyz.atlassian.net/*'

We have exceeded some quotas as mentioned under https://developer.atlassian.com/platform/forge/platform-quotas-and-limits/, especially number of API calls per invocation and number of log lines.

Can it be that our app has been suspended and that’s why the trigger is not fired? How can we know that our app has been suspended if this is the case?

Another explanation would be that we might have made a programming mistake

index.jsx

export { default as runWebtrigger } from './webtrigger';
export { default as runScheduledtrigger } from './scheduledtrigger';

Can two exported functions have the same name?

Thank you in advance.

Regards,
Kevin

2

Hi @KevinSuter

Do you mind sharing your appId so we can investigate a bit more on our side?

As for the code question, did you try testing with forge tunnel and invoking the function as a webtrigger instead? (so you can confirm the code is working as expected)

Hope this helps.

Regards,
Xavier