Apify Discord Mirror

Updated 2 months ago

Dataset FIELDS attribute

At a glance

The community member is having an issue with an integration actor that relies on the 1FIELDS1 attributes from the input dataset, which are not being populated immediately when retrieving data from the API at https://api.apify.com/v2/datasets/{dataset_id}. Even after looping up to 20 times with a 5-second interval, the FIELDS attributes are sometimes still not populated. The community member is asking for feedback on whether they are missing something or if there is a better way to handle this issue.

In the comments, another community member suggests that the issue could be a bug and asks the original poster to share the dataset ID. Another community member comments that the dataset has gone, but it happens less often now.

There is no explicitly marked answer in the provided information.

Useful resources
I have an integration actor that relies on the 1FIELDS1 attributes from the input dataset (payload). I retrieve this data by pulling from the API https://api.apify.com/v2/datasets/{dataset_id}, but it seems that the FIELDS attributes are not populated immediately. Even after looping up to 20 times with a 5-second interval, sometimes they still aren't populated. Am I missing something, or is there a better way to handle this? Any feedback would be really appreciated. Thank you!

Plain Text
βŒ› ... pending #1 (158 rows, 0 fields)
βŒ› ... pending #2 (158 rows, 0 fields)
βŒ› ... pending #3 (158 rows, 0 fields)
βŒ› ... pending #4 (158 rows, 0 fields)
βŒ› ... pending #5 (158 rows, 0 fields)
βŒ› ... pending #6 (158 rows, 0 fields)
βŒ› ... pending #7 (158 rows, 0 fields)
βŒ› ... pending #8 (158 rows, 0 fields)
βŒ› ... pending #9 (158 rows, 0 fields)
βŒ› ... pending #10 (158 rows, 0 fields)
βŒ› ... pending #11 (158 rows, 0 fields)
βŒ› ... pending #12 (158 rows, 0 fields)
βŒ› ... pending #13 (158 rows, 0 fields)
βŒ› ... pending #14 (158 rows, 0 fields)
βŒ› ... pending #15 (158 rows, 0 fields)
βŒ› ... pending #16 (158 rows, 0 fields)
βŒ› ... pending #17 (158 rows, 0 fields)
βŒ› ... pending #18 (158 rows, 0 fields)
βŒ› ... pending #19 (158 rows, 0 fields)
βŒ› ... pending #20 (158 rows, 0 fields)
❌ Error: Dataset EMPTY or COLUMNS unavailable!
L
!
2 comments
Can you share an ID of the dataset? That looks like a bug if you indeed have non-empty items
the datasets has gone πŸ˜“ but It happens less often now
Add a reply
Sign up and join the conversation on Discord